unexpected problem of bind-8.2.2-p7

[Zhao Yue]

Hi

I recently upgrated a dns server in a solaris2.6 machine from bind-8.2.2-p3 to bind-8.2.2-p7.
It appeared quite well for a few days. However, today afternoon, it suddenly start hanging,
dumping out the following messages continuously.

Dec 12 11:11:58 xxxxx named[8804]: sysquery: no addrs found for root NS ()
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(A.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(H.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(C.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(G.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(F.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(B.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(J.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(K.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(L.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(M.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(I.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(E.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS
(D.ROOT-SERVERS.NET)
Dec 12 11:12:23 xxxxx named[8804]: ns_req: no address for root server
Dec 12 11:12:23 xxxxx named[8804]: sysquery: no addrs found for root NS ()
Dec 12 11:12:25 xxxxx named[8804]: sysquery: no addrs found for root NS
(A.ROOT-SERVERS.NET)
Dec 12 11:12:25 xxxxx named[8804]: sysquery: no addrs found for root NS (H.RO
OT-SERVERS.NET)
...

Meanwhile, nslookup gave the message "Server failed" on any query.
After the named was restarted by "ndc restart", everything was recovered.

I did not find any unusualness of the machine, nor could I detect any network
problems. A neighboring DNS server was running well at the same time. Since
it had never happened by the previous versions of bind, I just guess it may be
a bug of the new version. Is there anybody who had a similar experience?
What is most likely the reason of the problem?

Thanks.

--
Zhao Yue
SECOM TrustNet