In message <h4ofir$rt...@ger.gmane.org>, Chris Hills writes: > Hi > > After changing configuration from "listen-on-v6 { any; };" to using > specific addresses, I observed the following in the log after issuing > `rndc reload` (times are CEST):- > > 29-Jul-2009 04:44:22.893 network: error: binding TCP socket: address in use > 29-Jul-2009 04:44:22.893 network: error: binding TCP socket: address in use > 29-Jul-2009 04:44:22.893 network: info: no longer listening on ::#53 > 29-Jul-2009 04:44:22.965 general: info: reloading configuration succeeded > 29-Jul-2009 04:44:23.031 general: info: reloading zones succeeded > 29-Jul-2009 05:19:10.179 general: info: received control channel command > 'reload' > 29-Jul-2009 05:19:10.180 general: info: loading configuration from > '/usr/local/bind/9.6.1-P1/etc/named.conf' > 29-Jul-2009 05:19:10.182 general: info: using default UDP/IPv4 port > range: [1024, 65535] > 29-Jul-2009 05:19:10.182 general: info: using default UDP/IPv6 port > range: [1024, 65535] > 29-Jul-2009 05:19:10.194 general: info: reloading configuration succeeded > 29-Jul-2009 05:19:10.194 general: info: reloading zones succeeded > > After the reload, BIND no longer listened on tcp sockets, but udp > sockets worked ok. After restarting named, it was listening on tcp > sockets once more. Based on the log it looks like it is trying to bind > to the address-specific tcp sockets before releasing tcp [::]:53.
Linux's IP stack is broken. Reloading a second time would have fixed it. > BIND is 9.6.1-P1 on Linux x86. > > Regards, > > Chris > > _______________________________________________ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users