'Named' not listening on reboot, Works ok on 'named' restart

[dalydesign]

Whenever I reboot the server, no websites show. The DNS service appears not to be working.

If I enter:
/etc/init.d/named status

Named is running but still no websites showing.

When I restart named the website come online instantly:
/etc/init.d/named restart

I do not know why it is creating such problems.

Tried bootstrapper repair - does not fix it.

 

[dalydesign]

When I reboot server I get this:

# netstat -ntpl | grep named
tcp        0      0 127.0.0.1:53                0.0.0.0:*                   LISTEN      2720/named
tcp        0      0 127.0.0.1:953               0.0.0.0:*                   LISTEN      2720/named
tcp        0      0 :::53                       :::*                        LISTEN      2720/named

I then restart Named Service and it runs normally:

# /etc/init.d/named restart
Stopping named: .                                          [  OK  ]
Starting named:                                            [  OK  ]


# netstat -ntpl | grep named
tcp        0      0 88.208.221.101:53           0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.13:53           0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.12:53           0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.11:53            0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.10:53            0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.9:53            0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.222.201:53            0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.8:53            0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.7:53            0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.6:53            0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.5:53            0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.4:53            0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.3:53            0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.2:53            0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.223.1:53            0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 88.208.221.100:53           0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 127.0.0.1:53                0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 127.0.0.1:953               0.0.0.0:*                   LISTEN      7447/named
tcp        0      0 :::53                       :::*                        LISTEN      7447/named

There is no errors in /var/log/messages

Any help would be appreciated.

Thanks

 

[IgorG]

no websites showing

What do you mean exactly? What sort of errors you have?

 

[dalydesign]

I reboot the server (for whatever reason). The server loads as per normal. If I type in the IP Address for a site (i.e. 88.208.221.2) the website displays, but if I use www.mydomain.com it does not resolve. So I restart etc/init.d/named and then I can view the website via www.mydomain.com

If I run netstat straight after a server reboot, its only listening on 127.0.0.1 : 53
But when I restart /etc/init.d/named then it starts listening to all the ip addresses (see previous post).

When I look in var/log/messages it shows no errors.

This is the timeline of events with the logfile messages:

When I reboot and the server closes everything, it shows that its no longer listening...
Oct 23 00:19:28 server88-208-221-1 named[26277]: no longer listening on 88.208.223.2#53

Then when the server comes back online theres nothing new in the log file (no errors, and nothing to say that its listening to any IP addresses). I can view my website by typing http://88.208.221.2/ but not accessible if I type in http://www.mydomain.com/

So after a few minutes of no websites resolving, I run the command '/etc/init.d/named status' and it shows named as 'up and running' but theres still no websites showing when I type in www.mydomain.com in the web browser.

I then run the command '/etc/init.d/named restart' and the websites start to appear when we use www.mydomain.com. Then in the logfiles, it shows that its started listening...

Oct 23 00:24:15 server88-208-221-1 named[6143]: listening on IPv4 interface eth0:6, 88.208.223.2#53​

Does this make sense?

This is not normal as it should be listening when I reboot the server.

 

[UFHH01]

Hi Paul_Daly,

at the moment, there is an open bug with watchdog ( #PPPM-1898 for your reference ).
Please consider to read and follow:

Error during restart in Plesk 12 Watchdog modules ( KB - article 126 083 )​

 

[dalydesign]

Thanks.
I thought that was just watchdog specific?
or does it relate to other services (named)?

 

[KristianM]

Hi Paul,

is it possible that the network interfaces are not all up when named tries to start?
It might not be able to bind to all the IPs you have if they are not up yet.

Maybe you could try adding "/etc/init.d/named restart"
to the following file: /etc/rc.local (before the "exit 0").

This should cause your named to restart again after everything else has started up after a reboot or power up.

Regards,
Kristian

 

[dalydesign]

Strangely! That didn't work.

 

[KristianM]

Hi,

could you please check that the network incl. all your IPs are up when restarting?
I just think your network takes to long to be ready.

Maybe add an extra sleep 60 before the restart in rc.local?
I know this is only a dirty workaround. But I do not think this is Plesk related in any way.

Regards,
Kristian

 

[dalydesign]

The IP's are up and running as I can access them straight away via http://88.208.221.2/

I have also left the server for an hour and the websites are still offline.

I added the sleep 60 in rc.local and this did not work. It still requires manual restart.

It's worth noting that any website that does not use the DNS is not affected as we can access no problem whatsoever (i.e. if nameserver is hosted elsewhere and A records are pointed to our server, then website shows ok)