Strange bind9 problem on dual stacked box
-----BEGIN PGP SIGNED MESSAGE-----
I have a very strange problem on one of my dual stacked nameservers.
The box is running bind 9.2.1-2.woody and kernel-image 2.4.18-5 686
whenever I start bind it complains that it can't bind to port 53 TCP
on the IPv4 interfaces but starts up completely and works OK.
lsof | grep TCP | grep -i domains tells me that there is nothing
running on port 53 TCP on IPv4.
I created a new kernel-image 2.4.18-5 with USAGI patches that works
perfect on my two other dual stacked nameservers (who don't have that
strange binding behavior) but as soon as I reboot the other box
named aborts startup.
And I get two messages that I don't get with the old kernel
- - --snip---
named: could not get query source dispatcher
named: exiting (due to fatal error)
- - --snip---
the /etc/bind/named.conf is identical to the one used on the
2 other servers (just copied it)
the only difference that I know about is that lwresd was
installed on the strange behaving box. I purged it as soon as
I noticed that.
thanks for your help
- - --
Institute for Computer and Network Security
WWW : http://www.x-tec.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org