sysquery: no addrs found for root NS

[Kevin Darcy]

Hmmmm... I'm pretty stumped on this one. Usually "no addrs found for root
NS" means that you can't talk to the root servers, which in turn is usually
caused by a networking/connectivity/firewall problem. But such problems
should have nothing to do with enabling Dynamic Update for a zone. Are you
sure it wasn't just a coincidence that this happened right after you
enabled Dynamic Update? If you manually do a root NS query from this box,
does it work?


- Kevin

Riley McIntire wrote:

> Running named 8.2.3-REL on fbsd 4.3-R.
> After changing a zone to dynamic in named.conf, in addition to the one
> already there, "no addrs found" errors started. Going back to the old
> configuration didn't stop it. Aside from the syslog errors the server
> seem to work fine and has been working for some time. The old conf file
> wasn't restored from backup--just commented out the update line as
> below. A number of searches didn't turn up anything that seemed
> pertinent.
> Sample errors:
> Oct 15 12:27:36 aji named[100]: sysquery: no addrs found for root NS
> (anshar.shadow.net)
> Oct 15 12:27:36 aji named[100]: sysquery: no addrs found for root NS ()
> Oct 15 12:27:36 aji named[100]: sysquery: no addrs found for root NS
> (localhost)
> Just in case I got the latest cache file from internic.net. The "root
> NS" in the error log, eg "localhost" also seems strange...
>
> named.conf entries:
> zone "." {
> type hint;
> file "db.cache";
> };
>
> Entry which was changed to dynamic (and back):
> zone "domain.com" {
> type master;
> file "master/domain.com";
> #allow-update {xxx.xxx.xxx/24 ; };
> };
>
> Any ideas?  A  cc to me of any reply would really help.  I can't seem to
> get
> this group updated since SBC screwed up their news server. Please note
> the "nospam" in address.
>
> Thanks,
> Riley