Hi. We're getting this error frequently with the DNS Server and we've
searched the Knowledgebase but found nothing but we'll search harder again

Error found in named.run:

general: main: notice: starting BIND 9.2.0
general: dns/db: critical: Unable to access RootServerInfo Object
general: dns/db: critical: Unable to get RootServerInfo fdn with error 25
general: dns/hints: warning: Loading Root data from directory Failed
general: dns/zone: warning: zone 16.172.IN-ADDR.ARPA/IN: expired
general: main: critical: zone.c:2421: REQUIRE(!((zone)->locked)) failed
general: main: critical: exiting (due to assertion failure)
general: main: notice: exiting
6.172.IN-ADDR.ARPA/IN: expired
general: dns/zone: warning: zone 16.172.IN-ADDR.ARPA/IN: expired


When we get the
general: main: critical: zone.c:2421: REQUIRE(!((zone)->locked)) failed
Named.nlm quits working and we have to reload the Named.nlm again.

We have an existing dns server, the server we're working on will replace
the existing DNS Server. Both the new and existing dns server are
authorative dns servers. Is that an issue? Is it why we are getting zone
locked errors? We have checked the SOA information for the reverse lookup
zone and were trying to figure out why the reverse lookup zone expires.
Here's the information on the SOA tab
Refresh 180
Retry 60
Exprie 168
Min TTL 24.

We've been experiencing the lock error almost every other day.
The new server we're working on is NW65SP3; Named v6.04.10.

Any inputs will be appreciated...

Thanks