Date: Thu, 29 Jan 2004 17:16:40 -0800 From: Mark Edwards <mark@antsclimbtree.com> To: questions@FreeBSD.ORG Subject: BIND 8.3 going insane on FreeBSD 4.9 Message-ID: <F53D82B1-52C1-11D8-B33B-000393C0ABC0@antsclimbtree.com>
next in thread | raw e-mail | index | archive | help
So, I've seen this twice now. BIND completely flips its lid and utterly destroys the server. Logs say: 29-Jan-2004 16:48:34.559 default: warning: sysquery: no addrs found for root NS (K.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.559 default: warning: sysquery: no addrs found for root NS (D.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (A.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (H.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (C.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (G.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs found for root NS (F.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs found for root NS (B.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs found for root NS (J.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (K.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (M.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (I.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (L.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs found for root NS (D.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs found for root NS (A.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs found for root NS (H.ROOT-SERVERS.NET) My root hints are up to date, and I've seen this both using forwarders and not. I've read that this is some incompatibility between BIND 8.3 and other servers. Is the only solution to this problem to run BIND 9? I really have to make sure this doesn't happen again, because it has catastrophic effects on the server. Thanks for any help!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F53D82B1-52C1-11D8-B33B-000393C0ABC0>