Hi,

Today, I had a very strange behavior with named. I had a few
thousand entries in my messages file of this:

Aug 30 22:22:52 defiant named[117]: sysquery: no addrs found for root NS (J.ROOT-SERVERS.NET)
Aug 30 22:22:52 defiant named[117]: sysquery: no addrs found for root NS (K.ROOT-SERVERS.NET)
Aug 30 22:22:52 defiant named[117]: sysquery: no addrs found for root NS (L.ROOT-SERVERS.NET)
Aug 30 22:22:52 defiant named[117]: sysquery: no addrs found for root NS (M.ROOT-SERVERS.NET)
Aug 30 22:22:52 defiant named[117]: sysquery: no addrs found for root NS (A.ROOT-SERVERS.NET)
Aug 30 22:22:52 defiant named[117]: sysquery: no addrs found for root NS (B.ROOT-SERVERS.NET)
Aug 30 22:22:52 defiant named[117]: sysquery: no addrs found for root NS (C.ROOT-SERVERS.NET)
Aug 30 22:22:52 defiant named[117]: sysquery: no addrs found for root NS (D.ROOT-SERVERS.NET)
Aug 30 22:22:52 defiant named[117]: sysquery: no addrs found for root NS (E.ROOT-SERVERS.NET)
Aug 30 22:22:52 defiant named[117]: sysquery: no addrs found for root NS (F.ROOT-SERVERS.NET)
Aug 30 22:22:52 defiant named[117]: sysquery: no addrs found for root NS (G.ROOT-SERVERS.NET)
Aug 30 22:22:52 defiant named[117]: sysquery: no addrs found for root NS (H.ROOT-SERVERS.NET)

It was not possible, to do any queries. ndc reload didn't work
either. After I killed named, I started it again and it's working
fine again.

Any ideas, what was going wrong here? Bind was running a few
months without any troubles and I didn't changed the
configuration.



Regards, Ihsan...

-- 
Swiss Unix User Group: http://www.suug.ch/
Software Packages for Solaris: http://www.blastwave.org/