Multihomed BIND will not respond to 2nd address
michael at kjorling.com
Wed Oct 31 21:34:28 UTC 2001
-----BEGIN PGP SIGNED MESSAGE-----
Don't forget that on UNIX systems, you have to be root to bind to
ports < 1024. Very few people should even be considering running BIND
as root, especially given BIND 9's very simple chroot setup (-t <path>
and that's about it).
On Oct 31 2001 21:19 -0000, Barry Margolin wrote:
> >I have used the "listen-on" configuration directive in named.conf to tell
> >BIND to listen on both addresses.
> >My problem is: I cannot get BIND to respond to any requests from any other
> >machine on the IP address in the new address space, but it responds
> >beautifully on the old IP.
> Do you start BIND before or after you configure the second IP? If you
> start it before enabling the second NIC, it won't be able to bind to that
> IP. Every hour (by default) BIND scans the configured interface list and
> updates its bindings to match what exists.
Michael Kjörling -- Programmer/Network administrator ^..^
PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e \/
Internet: michael at kjorling.com -- FidoNet: 2:204/254.4
"There is something to be said about not trying to be glamorous
and popular and cool. Just be real -- and life will be real."
(Joyce Sequichie Hifler, September 13 2001)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Public key is at http://michael.kjorling.com/contact/pgp.html
-----END PGP SIGNATURE-----
More information about the bind-users