Bind named to 0.0.0.0 (INADDR_ANY)

[Mark Andrews]

In message <cbf1a1340809301028o3ffc5e71ua6a38d7aaefeedca at mail.gmail.com>, "Rich
ard Wall" writes:
> 2008/9/30 Mark Andrews <Mark_Andrews at isc.org>:
> > In message <cbf1a1340809300721j468531d5sa5da8bedb3fff47e at mail.gmail.com>, "
> Rich
> > ard Wall" writes:
> <snip>
> >> I've tried:
> >> listen-on { 0.0.0.0; };
> >        Which is "listen-on { 0.0.0.0/32; };" which won't match any
> >        interface's address.
> 
> Hi Mark,
> 
> Understood.
> 
> <snip>
> >> listen-on { any; };
> >> listen-on { localhost; };
> >> listen-on { localnets; };
> >> These explicitly bind named to the configured local IP addresses.
> >> Is there another way to do this?
> >
> >        No. Named listens on individual interfaces so that the reply
> >        traffic comes from the correct address.
> >
> 
> Okay, thanks for the prompt response. We were looking for a convenient
> way to use multiple source and destination addresses with dns views,
> but we can just explicitly configure all the IPs that we're going to
> use.
> 
> Out of interest, how do other services get round this? For example I
> notice that ntpd is listening on IPv4 0.0.0.0:123; doesn't it have the
> same issue?

	Yes and the same solution was used. :-)

% netstat -na | grep 123
udp4       0      0  127.0.0.3.123          *.*                    
udp4       0      0  127.0.0.2.123          *.*                    
udp4       0      0  10.53.0.7.123          *.*                    
udp4       0      0  10.53.0.6.123          *.*                    
udp4       0      0  10.53.0.5.123          *.*                    
udp4       0      0  10.53.0.4.123          *.*                    
udp4       0      0  10.53.0.3.123          *.*                    
udp4       0      0  10.53.0.2.123          *.*                    
udp4       0      0  10.53.0.1.123          *.*                    
udp4       0      0  127.0.0.1.123          *.*                    
udp6       0      0  fe80:4::1.123          *.*                    
udp6       0      0  ::1.123                *.*                    
udp6       0      0  fe80:2::216:6fff.123   *.*                    
udp6       0      0  fe80:1::214:22ff.123   *.*                    
udp6       0      0  *.123                  *.*                    
udp4       0      0  *.123                  *.*                    
% 

	IPv6 and can use the advanced ipv6 api and packet info
	to make sure the response comes from the right address.

> 
> -RichardW.
> -- 
> Richard Wall
> Support Engineer
> ApplianSys Ltd
> http://www.appliansys.com
> 
> (t) +44 (0)24 7643 0094
> (f) +44 (0)87 0762 7063
> (e) richard.wall at appliansys.com
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org