Server Not Resolving Names

snowweb

snowweb

Verified User
Joined
Aug 31, 2007
Messages
144
Location
Antipolo City, Rizal, Philippines (a British Natio
Everything has been working fine until today.

I noticed this evening that there are some emails stuck in the que including one which I sent earlier to a yahoo address.

According to the retry errors recorded, name resolution was not occurring properly.

I connected to the server using SSH and pinged google.com and it said unknown host. I also tried pinging a domain hosted on our server and that failed too.

When I first noticed the problem, I checked named and it had stopped running. I restarted the VPS container and also rebooted DA but Named didn't start due to an error. Eventually, either I managed to start it or it restarted automatically but although it's now running, it still is not resolving names!

In a bid to see what has changed on the server, I sorted the files in /etc by date modified and noticed that early this morning both /etc/hosts and etc/hosts.conf were modified.

I examined them both and noticed that hosts.conf has the following contents:
nameserver 64.235.53.251
Click to expand...

I don't recognize the IP address. It's not one of ours. Is this the problem? If so what caused it and how do I correct it?

If not, please can someone show me where to look next?

Thanks in advance :)

pete
 
The reverse hostname of IP address (64.235.53.251) resolves to: serverpoint.com

It is probably the DNS nameserver at your VPS provider.
 
I have some more info...

The following are the last few lines of /var/log/messages:

Sep 24 21:50:51 s1 named[11522]: starting BIND 9.3.3rc2
Sep 24 21:50:51 s1 named[11522]: found 8 CPUs, using 8 worker threads
Sep 24 21:50:51 s1 named[11522]: loading configuration from '/etc/named.conf'
Sep 24 21:50:51 s1 named[11522]: listening on IPv4 interface lo, 127.0.0.1#53
Sep 24 21:50:51 s1 named[11522]: binding TCP socket: address in use
Sep 24 21:50:51 s1 named[11522]: listening on IPv4 interface venet0:0, 216.108.227.20#53
Sep 24 21:50:51 s1 named[11522]: binding TCP socket: address in use
Sep 24 21:50:51 s1 named[11522]: listening on IPv4 interface venet0:1, 216.108.227.21#53
Sep 24 21:50:51 s1 named[11522]: binding TCP socket: address in use
Sep 24 21:50:51 s1 named[11522]: listening on IPv4 interface venet0:2, 216.108.227.22#53
Sep 24 21:50:51 s1 named[11522]: binding TCP socket: address in use
Sep 24 21:50:51 s1 named[11522]: listening on IPv4 interface venet0:3, 216.108.227.23#53
Sep 24 21:50:51 s1 named[11522]: binding TCP socket: address in use
Sep 24 21:50:51 s1 named[11522]: /etc/named.conf:23: couldn't add command channel 127.0.0.1#953: address in use
Sep 24 21:50:52 s1 named[11522]: couldn't open pid file '/var/run/named/named.pid': Permission denied
Sep 24 21:50:52 s1 named[11522]: exiting (due to early fatal error)
Click to expand...

Is this relevant?
 
Suddenly name resolution appears to have started working again!! I guess it must have been a problem with the upline DNS server of my ISP (serverpoint) although there is nothing about it in their news section on their site.

Anyway, thanks for you help. :)

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