Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Jan 2004 07:18:11 +0100
From:      Richard van Vliet <rvv@inter-sprint.nl>
To:        'Mark Edwards' <mark@antsclimbtree.com>
Cc:        "'questions@freebsd.org'" <questions@freebsd.org>
Subject:   RE: BIND 8.3 going insane on FreeBSD 4.9
Message-ID:  <26EA03471FA2D711A7D60050DA61CE50064E3B@mickey.inter-sprint.nl>

next in thread | raw e-mail | index | archive | help
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:mark@antsclimbtree.com] 
> Verzonden: vrijdag 30 januari 2004 2:17
> Aan: questions@freebsd.org
> 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!
> 
> _______________________________________________
> freebsd-questions@freebsd.org mailing list 
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to 
> "freebsd-questions-unsubscribe@freebsd.org"
> 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26EA03471FA2D711A7D60050DA61CE50064E3B>