Named sysquery errors.

Dan Mahoney google at gushi.org
Wed Jan 14 20:38:37 UTC 2004


I'm running 8.3.4.-RELEASE under FreeBSD-STABLE.  I have one named
process that every couple of weeks, with no real regularity, starts
sending out MASSIVE amounts of errors:

Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (A.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (H.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (C.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (B.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (G.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (F.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (B.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (K.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (M.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (I.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (E.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (A.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (H.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (C.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (J.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (G.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (F.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (B.ROOT-SERVERS.NET)
Jan 14 15:34:44 prime named[59825]: sysquery: no addrs found for root
NS (J.ROOT-SERVERS.NET)
J

This slams syslogd, and drives the system load so high that sendmail
shuts down.  The "fix" is to kill -9 and restart the process.

And only one named process does it, and only every couple of weeks.

Any ideas?


More information about the bind-users mailing list