DNS that doesnt..

[Mountainman]

This is kinda strange. I tried to setup a dns server last night and this morning. I got no errors when it reboots from the messages log. I can do a nslookup or digs, and they work fine. Whenever I try to open a webpage, it wont resolve. Its the exact same files I had on there last time, and it worked perfectly. I am at work, so I cant post the files, but if anyone has any ideas, I will definitely entertain them.

[bdg1983]

And /etc/resolv.conf is setup properly?

Verify that the dns and domain/search are correct in the file.

[Mountainman]

Going off of memory, the resolv.conf file has search mydomain.name and then in the next line has nameserver 192.168.0.1 .

[ 27 March 2001: Message edited by: Mountainman ]

[bdg1983]

You need the isp's nameservers in resolv.conf

[Lorithar]

*grins* and swats mdwatts gently

He's using his own nameserver.

Mountain: You can dig@ and nslookup .. but cant surf... Do you have the listen on: directive set to your inside IP address? .. I seriously DON"T reccommend setting it to 0.0.0.0 ... but IF you have it set to inside IP and are trying to surf from the server, you may want to add listen on :127.0.0.1 as well .. I found that with 8.2.23pl5 that it didn't listen to the local requests although it resolved downstream requests just fine... it caused some serious weirdness as it appears that one of the inner loops on bind issues its own requests to the loopback address...

[Mountainman]

Yeah I think I had several probs with my setup. I did a default install of the dns when I reinstalled drake 6.1 and I think it did a bind 4X install instead of the bind 8x. I installed the bind 8 rpm and (duh on my part) added the computer to the 192.168.0 reverse mapping file in /var/named and miraculously (duh again) it was able to tell itself who it was.. Now I am fighting masquing for some reason. Thanks for the info though!