Re: BIND 8.3 going insane on FreeBSD 4.9
Howdy, I found this report from Mark Edwards after searching for a fix/cause via The freebsd-questions Archive to deal with the same incident taking place on my FreeBSD box today! After reading about a fix/patch regarding inconsistency between Bind8 and Bind9 at - http://www.freebsd.org/cgi/query-pr.cgi?pr=61647 posted by Melvyn Sopacua my first question is - what command will output the version of bind I currently _am_ running? I think it is at Ver 9 but have been unable to dig that up. Here is some of the info I have so far, sorry for the length but figure the content included will probably answer some questions in advance. ___ uname -a == FreeBSD davez.org 4.9-RELEASE-p1 FreeBSD 4.9-RELEASE-p1 #2: __ snip from /var/log/messages.0.gz___ Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (a.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (c.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (e.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (f.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (g.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (h.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (i.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (j.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (k.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (l.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (m.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (a.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (a.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (e.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (f.root-servers.net) end snip_ My log file gets so big it just keeps rolling over due to size causing the /var directory to fill up and report the disk is full or out of space. __Snip from dmesg.today_ pid 81 (syslogd), uid 0 on /var: file system full pid 26444 (gzip), uid 0 on /var: file system full to deal with this I simply emptied the huge messages files with : filename where filename == messages.x.xx in the /var/log dir. ***The roll over just happened again == #wc messages.0.gz 73 823 69613 messages.0.gz Other than just shutting the box down, can anyone provide a solution to this PROBLEM? I googled/searched around and found a couple of attempts to correct this issue by others which included downloading a new updated named.root file and putting it in the /etc/namedb dir or changing instructs to resolvers only which were supposed to have corrected the issue for some, but didn't work for me. I'm in no way a top notch guru with FreeBSD but am willing to learn. So far all the man ***.xxx or cat xxx.*** efforts have failed me on this issue. Any help anyone can provide/suggest would be very appreciated. Dave Lajoie [EMAIL PROTECTED] On Thu, 29 Jan 2004, Mark Edwards wrote: 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
Re: BIND 8.3 going insane on FreeBSD 4.9
Howdy, I found this report from Mark Edwards after searching for a fix/cause via The freebsd-questions Archive to deal with the same incident taking place on my FreeBSD box today! After reading about a fix/patch regarding inconsistency between Bind8 and Bind9 at - http://www.freebsd.org/cgi/query-pr.cgi?pr=61647 posted by Melvyn Sopacua my first question is - what command will output the version of bind I currently _am_ running? I think it is at Ver 9 but have been unable to dig that up. Here is some of the info I have so far, sorry for the length but figure the content included will probably answer some questions in advance. ___ uname -a == FreeBSD davez.org 4.9-RELEASE-p1 FreeBSD 4.9-RELEASE-p1 #2: __ snip from /var/log/messages.0.gz___ Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (a.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (c.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (e.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (f.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (g.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (h.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (i.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (j.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (k.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (l.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (m.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (a.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (a.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (e.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (f.root-servers.net) end snip_ My log file gets so big it just keeps rolling over due to size causing the /var directory to fill up and report the disk is full or out of space. __Snip from dmesg.today_ pid 81 (syslogd), uid 0 on /var: file system full pid 26444 (gzip), uid 0 on /var: file system full to deal with this I simply emptied the huge messages files with : filename where filename == messages.x.xx in the /var/log dir. ***The roll over just happened again == #wc messages.0.gz 73 823 69613 messages.0.gz Other than just shutting the box down, can anyone provide a solution to this PROBLEM? I googled/searched around and found a couple of attempts to correct this issue by others which included downloading a new updated named.root file and putting it in the /etc/namedb dir or changing instructs to resolvers only which were supposed to have corrected the issue for some, but didn't work for me. I'm in no way a top notch guru with FreeBSD but am willing to learn. So far all the man ***.xxx or cat xxx.*** efforts have failed me on this issue. Any help anyone can provide/suggest would be very appreciated. Dave Lajoie [EMAIL PROTECTED] On Thu, 29 Jan 2004, Mark Edwards wrote: 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
Re: BIND 8.3 going insane on FreeBSD 4.9
On Fri, 13 Feb 2004, questions wrote: Howdy, I found this report from Mark Edwards after searching for a fix/cause via The freebsd-questions Archive to deal with the same incident taking place on my FreeBSD box today! After reading about a fix/patch regarding inconsistency between Bind8 and Bind9 at - http://www.freebsd.org/cgi/query-pr.cgi?pr=61647 posted by Melvyn Sopacua my first question is - what command will output the version of bind I currently _am_ running? krazykat# named -v named 8.3.4-REL Thu Apr 3 08:26:42 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/usr.sbin/named m I think it is at Ver 9 but have been unable to dig that up. Here is some of the info I have so far, sorry for the length but figure the content included will probably answer some questions in advance. ___ uname -a == FreeBSD davez.org 4.9-RELEASE-p1 FreeBSD 4.9-RELEASE-p1 #2: __ snip from /var/log/messages.0.gz___ Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (a.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (c.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (e.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (f.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (g.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (h.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (i.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (j.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (k.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (l.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (m.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (a.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (a.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (e.root-servers.net) Feb 13 16:17:41 zeus named[83]: sysquery: no addrs found for root NS (f.root-servers.net) end snip_ My log file gets so big it just keeps rolling over due to size causing the /var directory to fill up and report the disk is full or out of space. __Snip from dmesg.today_ pid 81 (syslogd), uid 0 on /var: file system full pid 26444 (gzip), uid 0 on /var: file system full to deal with this I simply emptied the huge messages files with : filename where filename == messages.x.xx in the /var/log dir. ***The roll over just happened again == #wc messages.0.gz 73 823 69613 messages.0.gz Other than just shutting the box down, can anyone provide a solution to this PROBLEM? I googled/searched around and found a couple of attempts to correct this issue by others which included downloading a new updated named.root file and putting it in the /etc/namedb dir or changing instructs to resolvers only which were supposed to have corrected the issue for some, but didn't work for me. I'm in no way a top notch guru with FreeBSD but am willing to learn. So far all the man ***.xxx or cat xxx.*** efforts have failed me on this issue. Any help anyone can provide/suggest would be very appreciated. Dave Lajoie [EMAIL PROTECTED] On Thu, 29 Jan 2004, Mark Edwards wrote: 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
Re: BIND 8.3 going insane on FreeBSD 4.9
Well, I have any query allowed on my domains, and tcp/udp port 53 is open to all from any port. Is there anything else necessary to allow root queries? I generally don't have this problem; its only happened twice in 4 years, so it doesn't seem like a configuration issue on my end. I host public DNS for 10 domains. Will setting BIND to forward only really make any difference in this case? Does BIND still have to communicate with the root servers when dealing with its own domains? Does anyone know exactly what's causing this problem? Is it out-of-date root hints, or what? There seems to be some opinion on the net that this is a BIND 8 bug. On Jan 29, 2004, at 10:18 PM, Richard van Vliet wrote: Be sure that jou server can recieve query's directly from the rootservers, it happend at my place when the firewall blocked these rootname server query's. I had the same problem logs filling up in minutes... Configure your private BIND server to use forwarders only, it wil then query itself for its one zones and the forwarder for any other. Regards Richard. -Oorspronkelijk bericht- Van: Mark Edwards [mailto:[EMAIL PROTECTED] Verzonden: vrijdag 30 januari 2004 2:17 Aan: [EMAIL PROTECTED] Onderwerp: BIND 8.3 going insane on FreeBSD 4.9 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! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: BIND 8.3 going insane on FreeBSD 4.9
Be sure that jou server can recieve query's directly from the rootservers, it happend at my place when the firewall blocked these rootname server query's. I had the same problem logs filling up in minutes... Configure your private BIND server to use forwarders only, it wil then query itself for its one zones and the forwarder for any other. Regards Richard. -Oorspronkelijk bericht- Van: Mark Edwards [mailto:[EMAIL PROTECTED] Verzonden: vrijdag 30 januari 2004 2:17 Aan: [EMAIL PROTECTED] Onderwerp: BIND 8.3 going insane on FreeBSD 4.9 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! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
