Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Jan 2004 13:26:39 -0800
From:      Mark Edwards <mark@antsclimbtree.com>
To:        Richard van Vliet <rvv@inter-sprint.nl>
Cc:        "'questions@freebsd.org'" <questions@freebsd.org>
Subject:   Re: BIND 8.3 going insane on FreeBSD 4.9
Message-ID:  <FD7F5ED9-536A-11D8-885C-000393C0ABC0@antsclimbtree.com>
In-Reply-To: <26EA03471FA2D711A7D60050DA61CE50064E3B@mickey.inter-sprint.nl>
References:  <26EA03471FA2D711A7D60050DA61CE50064E3B@mickey.inter-sprint.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
Well, I have any query allowed on my domains, and tcp/udp port 53 is=20
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=20
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=20
really make any difference in this case?  Does BIND still have to=20
communicate with the root servers when dealing with its own domains?

Does anyone know exactly what's causing this problem?  Is it=20
out-of-date root hints, or what?  There seems to be some opinion on the=20=

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=20
> rootservers, it happend at my place when the firewall blocked these=20
> 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=20=

> 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.=A0 BIND completely flips its lid
> > and utterly destroys the server.=A0 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.=A0 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.=A0 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?FD7F5ED9-536A-11D8-885C-000393C0ABC0>