BIND 8.2.3 Error messages

Barry Margolin barmar at genuity.net
Wed Aug 29 21:59:47 UTC 2001


In article <9mjkfh$m8c at pub3.rc.vix.com>,
Nardis, Frank <nardis at TrendCS.com> wrote:
>
>
>I am running bind ver 8.2.3 with the INTERNIC root servers listed in my
>named.root file.  I have SEVERAL named sysquery errors in my messages file.
>
>Is something misconfigured?  If not what is the meaning of the message?
>
>
>named[5127]: sysquery: no addrs found for root NS
>(SCA04.AUTH.DNS.EXODUS.NET)
> named[5127]: sysquery: no addrs found for root NS
>(SCA03.AUTH.DNS.EXODUS.NET)
> named[5127]: sysquery: no addrs found for root NS ()
> named[5127]: sysquery: no addrs found for root NS
>(SCA04.AUTH.DNS.EXODUS.NET)
>named[5127]: sysquery: no addrs found for root NS
>(SCA03.AUTH.DNS.EXODUS.NET)

Are you using "forwarders"?  My first guess is that the machine you're
forwarding to has an incorrect list of root servers.  The named.root file
is just used to initialize the root server list, but one of the first
things that named does is send out a query to get the current list.  If you
have forwarders configured, this query will go there instead of one of the
real root servers.  If that server has a nonstandard root server list,
you'll cache that in place of the real roots.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list