okay, this one is strange to me.... all of a sudden my rh9 box stopped passing dns to the lan... it is set up as dhcp server and i use the dhcpd.conf to specify to use it as a dns server;

option domain-server mypc.com;

(i think that's the way the statement goes, anyways)

i have never had a problem with before, when i drop to command prompt on a pc on lan side, i can ping outside world using straight ip address numbers (i.e., 216.69.45.15), but if i type in a name to be resolved it will not do it! but it used to, no problem.... the rh9 box, itself (the one that has stopped passing the dns) has flawless internet connectivity... it can ping by straight dns for by name and can even surf net just fine w/ mozilla...

oh yeah, on lan pc's, when i run ipconfig /all it shows dns server as 209.123.16.2...but when i check the properties on rh9 box of eth0 (connected to internet) the dns servers are set to be obtained from isp and they are pri 24.196.17.8 & sec 67.97.48.9 (or something like that)...but the whole time in the past when it has worked with no problem, it has had the 209.123.16.2 as the dns server....why would it not show the two pri & sec dns servers and instead only show the 209.123.16.2 one? anyways, if i leave the lan pc's to obtain ip address via dhcp (which is working fine might i add), if i set the dns servers statically, the pri & sec listed above, i can have net access just fine...i can even drop to cmd prompt and ping using names!! plz give any suggestions... can't think of why all of a sudden dns would just stop getting passed to lan when nothing has been done to system to cause it...it just stopped! thanks in advance..



maze

I'm not exactly sure about RedHat but as far as i can remember about that...

Check your /etc/resolce.conf file....
And have you set up the dns-server right?

http://www.tldp.org/HOWTO/DNS-HOWTO.html

i have not even set up bind nor do i have it running...

these statements that make up my complete dhcpd.conf file has worked as far as having a dhcp, ofcourse, and a dns server up and working... as follows below;

ddns-update-style interim;

option domain-name-servers mypc.com;

option routers 10.0.0.1;

shared-network mypc.com {

subnet 10.0.0.0 netmask 255.0.0.0 {

range 10.0.0.2 10.0.0.100

}

}


the addr 10.0.0.1 under option routers is eth1 (lan side) nic...

by using the previous lines in my dhcpd.conf file, all dns info has been passed from isp, through rh9 box and onto clients on lan side via dhcp.... until now, for some strange reason! :P

i am unfamiliar w/ bind, but know what it is used for...do i need to try and run bind to see if that fixes the problem? even if it would, i would atleast like to know what made it stop all of a sudden.... thx!


maze

Presumably mypc.com points to 209.123.16.2
Is that the ip address of your rh9 box?

Did you change that from somthing like mazefire.dyndns.org
without telling us?

Why are you using mypc.com instead of 10.0.0.1 ?

Is the rh9 box really running a resolving nameserver?
Run nslookup, type "server mypc.com" then a domainname,
is it working?

the ip 209.123.16.2 is the dns server addr that is given to lan pc's via dhcp, instead of the pri & sec ip's, listed above, that are obtained from isp by rh9 box. why the lan pc's do not pick up the two pri & sec dns ip's, instead of 209.123.16.2, i have no idea...

the rh9 ip is obtained dhcp from isp...

i have not changed anything in dhcpd.conf or the name of rh9 box

mypc.com is the name of rh9 box and that is why i have "option domain-name-servers mypc.com" listed as the dns server in dhcpd.conf... and since nothing has changed and the dns ip info is still getting passed to lan pc's just as before, but the lan pc's all of a sudden cannot resolve names... :P

should i try changing "mypc.com" to 10.0.0.1? aren't they both the same thing when it comes to specifying who the dns server is?

i checked resolv.conf;

; generated by /sbin/dhclient-script
nameserver 24.196.17.8
nameserver 67.97.48.9

-- the two servers listed above are correct, but still no dice....

maybe i should just get a monkey, some thin, flat copper bars, extra wire and some green/red lights just for show...might make a better router than with the current lucky streak i'm running.... (yes, i've put a little thought into this)

If you want help you have to answer the questions you are asked.
I repeat, is 209.123.16.2 the ip address of your rh9 box?

If mypc.com is 209.123.16.2 then you should not be suprised when your clients send name lookup querys to 209.123.16.2 becaause that is exactly what you have told them to do.

The windows machines do not think "hmm maze_fire told us to send name lookup querys to 209.123.16.2 but we magically know that what he actually mean was that his linux box should give us a compleltly different setting and the dhcp server on the linux box should magically know to give us the settings it got from the ISP instead of what is specified in the dhcp servers confi file."

>should i try changing "mypc.com" to 10.0.0.1?

You said "and a dns server up and working... " do you mean your ISP's server or a server running on your rh9 box?

>should i try changing "mypc.com" to 10.0.0.1?
Only if you are actually running a resolving nameserver on your rh9 box.

I already asked you about that. Please answer the question.

thank you all for your help with this...but i found a solution....(which i think i had it wrong in the first place)...i replaced mypc.com with the pri & sec dns ip's....

option domain-name-servers 24.196.17.8, 67.97.48.9;

and everything is fine now! i still don't know why all of a sudden it stopped when using what i had before.... i don't know if maybe isp changed something on their end... possible?? anyways, the pri & sec dns ip's are now sent to all lan side pc's via dhcp, everyone can surf and run and hop, skip and play...whatever...i am better now!

thanks for all of the help, guys! later!!

maze