BIND does not listen at all when the interface is temporarily down (only with IPv6)

Chris Buxton cbuxton at
Wed Nov 18 22:14:27 UTC 2009

On Nov 18, 2009, at 8:36 AM, Stephane Bortzmeyer wrote:

> When I listen on one specific address:
> listen-on-v6 { 2001:db8::53;}; 
> If the interface is not UP at the time BIND starts, and therefore this
> IP address not local, BIND does not listen:
> 18-Nov-2009 17:31:24.588 not listening on any interfaces
> and does not resume if the interface becomes UP later. (I have to rndc
> reload.) Very annoying.
> This does not occur with IPv4 and the listen-on directive.

Yes it does. If you put named built from stock source on Mac OS X, enable the stock Apple launchd job for named, and restart, named will be deaf because the ethernet interface is not up by the time named starts. You have to reload it, or wait for the statistics interval, for it to come up on the Ethernet interface. (It will be listening on the loopback interface right away, though.)

If you use the "any" token in your listen-on-v6 list, instead of specific interfaces, it will listen on the wildcard interface. This way, it will start listening right away when the interface comes up. This is different than for the IPv4 stack.

Chris Buxton
Professional Services
Men & Mice

More information about the bind-users mailing list