restart named; missing TCP socket

Lightner, Jeff JLightner at
Wed Dec 12 13:27:15 UTC 2012

Why use rndc to stop then the init script to start?   Is there no /etc/rc.d/rc.named restart?   On RHEL5 the init script has a restart option so it will stop then start.

If a socket is open then it could take a finite amount of time for it to close making it unavailable on the restart if you haven't given it time enough to cleanup.

If no restart option in init maybe try to add a sleep to your command line:
Rndc stop;sleep 5;/etc/rc.d/rc.named start

-----Original Message-----
From: at [ at] On Behalf Of Tony Finch
Sent: Wednesday, December 12, 2012 8:20 AM
To: bind-users at
Subject: restart named; missing TCP socket

I have had a few instances recently when named has failed to re-open its TCP listening socket after a restart. This is particularly likely if I try to bounce it quickly with a command line like

# rndc stop; /etc/rc.d/rc.named start

The servers in question are recursive (apart from a few local zones) with simple ACLs. (I have had the same problem on servers with less simple ACLs too.)

        listen-on-v6   { ::1; };
        listen-on      {; };
        allow-query    { localhost; };
        allow-transfer { localhost; };

What do others do to avoid this problem?

f.anthony.n.finch  <dot at> Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good, occasionally poor at first.
Please visit to unsubscribe from this list

bind-users mailing list
bind-users at

Athena(r), Created for the Cause(tm)
Making a Difference in the Fight Against Breast Cancer

CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.

More information about the bind-users mailing list