Problem: Bind8.1.2/Irix/Ip-aliasing

Mark_Andrews at isc.org Mark_Andrews at isc.org
Tue Aug 3 23:58:43 UTC 1999


> In article <7o6o3s$d3n$1 at nnrp1.deja.com>,
> Berislav Todorovic  <BERI at etf.bg.ac.yu> wrote:
> >In article <Pine.GS4.4.05.9908021209070.6786-100000 at orion>, Jacob
> >Weismann Poulsen <jwp at dmi.dk> wrote:
> >
> >> A host with two ip-addresses for a single interface. Bind version
> >> 8.1.2 running on platform X must answer on both ip-addresses.
> >> ...
> >> I have tried to specify the IP-addresses that Bind should listen
> >> on by using the option listen on port 53 { ... }, but it doesn't
> >> change anything.
> >
> >Try the following:
> >
> >options {
> >   listen-on port 53 { any; };
> >};
> 
> Since that's the default, it seems unlikely to work.
> 
> >If it doesn't work, try to specify both interface addresses explicitly,
> >i.e.: "listen-on port 53 { 10.9.8.7; 10.1.2.3; };".
> 
> Someone else posted a similar problem a couple of weeks ago, and he had
> tried this solution as well.
> 
> It sounds like there's a bug in the code that tries to find all the virtual
> addresses on some operating systems.  I'm not surprised -- virtual
> addresses are something that every Unix vendor seems to have done
> differently (Solaris has logical interfaces, other OS's have IP aliases),
> so it's a challenge for a program like BIND to understand them all.
> 

	IRIX uses a different mechanism to most other vendors to
	get the addresses of the interfaces.  We have never been
	given a well integrated patch which does this.  By well
	integrated I mean "does not break other platforms".  The
	area of the code that does this look up is getnetconf() in
	src/bin/named/ns_main.c.

	We are always will to recieve patches.

	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org


More information about the bind-users mailing list