Upgraded bind, now not resolving

S

slander

Verified User
Joined
Mar 11, 2013
Messages
14
I upgraded bind/named this morning on a Debian 6 VPS, now the server won't resolve anything. named service is running. Config file looks good. Not sure if directadmin has anything to do with the bind startup process that's missing, or what might be going wrong. Any help would be greatly appreciated.


root@gator:~# ps aux|grep named
bind 2685 0.0 1.2 130564 12888 ? Ssl 18:43 0:00 /usr/sbin/named -u bind
root 12584 0.0 0.0 112312 832 pts/3 S+ 18:59 0:00 grep named
root@gator:~#
 
check /var/log/messages for errors

What do you get if you use the dig command to lookup a host? Are you talking about domains you host or recursive lookups such as google.com?

Try:

Code: 
dig @localhost google.com

or

Code: 
dig @localhost domain-you-host.com
 
No errors in /var/log/messages. The server won't even ping out. Other servers on the node can ping out. Just this particular cannot now for whatever random reason. Can't ping google.com, but can ping one of the IPs in their IP pool, (173.194.33.72) from the server. Odd.
 
You may be writing about two different problems.

If your nameserver can't resolve domain names on the box:

Make sure the named.conf file has the proper lines in it for each of your zones.

check:
Code: 
dig @localhost EXAMPLE.COM
replacing EXAMPLE.COM with the name of one of the domains

If you can't ping out, then ar eyou trying to ing an external location or one on the sever, and, specifically what error do you see?

Jeff
 
You must log in or register to reply here.
Back
Top