Listen on all interfaces

Danny Mayer mayer at gis.net
Sun Dec 21 18:36:08 UTC 2003


Oren Held <oren at held.org.il> wrote in message news:<brqle9$8to$1 at sf1.isc.org>...
> Hi,
> 
> I want my bind(9.2.3) to listen to all the interfaces - thus I do NOT
> include a "listen-on" line.
> However what it actually does is listen to EACH interface - which might
> sound fine at first thought - this means it listens to all the
> interfaces.
> 
> However, when I create a new interface I'd have to restart bind so it'll
> listen to it as well (I need it for HA reasons, sometimes I need to use
> another IP on the same machine). Unlike bind, most of the daemons I know
> don't listen to a specific interface.
> 

rndc reload will be sufficient to do this, IIRC. I was conducting a test a
while ago using the listen-on option in named.conf which explicitly included/
excluded a certain address. It would reconfigure itself just right every time
I reloaded.

the interface-interval value will in any case cause named rescan from time
to time and add or delete interfaces as necessary. You could always add a
value to named.conf and have the value changed to have it recheck more
frequently. I, in any case, see this happening when running BIND on a
dialup line and it will recheck.

> That's how it looks from lsof:
> 
> bind-style stuff which listen to EACH interface:
> named   213 bind   20u  IPv4    361       UDP localhost:domain 
> named   213 bind   22u  IPv4    363       UDP other_interface:domain 
> 
> Other daemons (the good behaviour..)
> ntpd      1091   root    4u  IPv4   3081       UDP *:ntp
> 
Well actually no. ntpd listening on every interface. It also listens on
the wildcard interface. It also never rescans for new interfaces. There
is a design for doing that but it's not yet implemented.

Danny
> 
> What do you think? Is it a 'bug'?
> 
>  - Oren


More information about the bind-users mailing list