Bind time up.

[Chris Buxton]

On Jul 23, 2011, at 1:22 AM, Vbvbrj wrote:

> Hello.
> 
> I have a server at home, that runs Bind 9 dns and routes internal traffic to internet. Its working fine. When I'm out of home, I disconnect my home switch. In bind log appears "no longer listening on 192.168.0.1#53". After a return to home and connecting switch, BIND does not respond to internal lan for long time till BIND start listening. Or I have to reload BIND service or reload configs with rndc.
> 
> How to tell BIND to not stop listening on cable disconnected adapters?

This might do it:

options {
	[...]
	interface-interval 0;
}

Untested. From the manual:

> interface-interval
> 	The server will scan the network interface list every interface-interval minutes. The default is 60 minutes. The maximum value is 28 days (40320 minutes). If set to 0, interface scanning will only occur when the configuration file is loaded. After the scan, the server will begin listen- ing for queries on any newly discovered interfaces (provided they are allowed by the listen-on configuration), and will stop listening on interfaces that have gone away.

Chris Buxton
BlueCat Networks