DNS server all the sudden acting weird

jasonswett · 09-29-2010, 12:51 PM

I have a DNS server that's been working just fine up until now. I have a local domain, "galapagos.office" set up, with several subdomains on it. I've been able to get to all the subdomains just fine for the last couple weeks from several different machines.

Now something weird's happening:
I CAN ping wiki.galapagos.office from a local machine
I CAN do an nslookup on wiki.galapagos.office from a local machine
I CAN see wiki.galapagos.office in a browser from a local machine

I CAN'T ping wiki.galapagos.office from the DNS server itself
I CAN'T do an nslookup on wiki.galapagos.office from the DNS server itself
I CAN'T see wiki.galapagos.office in a browser from the DNS server itself

And I COULD do all these things before. I don't know exactly when things went south because I almost never do anything from the DNS server itself.

Here's my db.galapagos.office:
http://pastebin.com/raw.php?i=nYJp39XA

Here's my db.192.168.140:
http://pastebin.com/raw.php?i=yU5yJ6K4

Here's my db.127.0.0:
http://pastebin.com/raw.php?i=Pqzy9Xhb

Here's my resolv.conf:

Code:

domain galapagos.office
nameserver localhost
#nameserver 68.87.77.130
#nameserver 68.87.72.130

Any idea what could be going wrong?

jasonswett · 09-29-2010, 12:53 PM

Here's one thing that may have made a difference: I recently restarted my DNS server. It seemed to have wiped out my resolv.conf but I put resolv.conf back. I don't know what else the restart may have affected, if anything.

jasonswett · 09-29-2010, 12:55 PM

And now, mysteriously, everything works again. Perhaps it was the fault of resolv.conf and the fix just took a while to kick in?

fancylad · 09-29-2010, 01:19 PM

Try changing your nameserver line in /etc/resolv.conf from:

Quote:

nameserver localhost

to:

Quote:

nameserver 127.0.0.1

Not sure if this is the problem but I had a similar dns issue where after I upgraded Slackware dns stopped working as the newer version of glibc no longer allows one to use a hostname for the "nameserver" line. It need to be an actual IP address. Again, I have no idea if this is the actual cause of your problem but you may want to try this.