Anyone have any suggestions on making Error: 35082 during NDS
operation go
away other than the measures taken in TID 10062166. What I've been
doing is
just unload named and then reloading it and the error goes away for a
while,
but usually when I come into work the next day the error has started
back
up. I know I'm just putting a band-aid on something that needs
stitches,
but I have several DNS zone objects to re-associate and I'm afraid of
the
implications of having the DNS server down for any amount of time due
to its
heavy use. The server is used as an internal DNS, then forwards
public
requests to our public DNS server. It's the first (primary) DNS
server
every device on the network hits before attempting to use the others.
So
server uptime is of utmost importance. The error does seem to hinder
access
or use of the DNS/DHCP services that it hosts. The only major change
to the
network that has taken place in the last month is an upgrade from NDS
8.85
to eDirectory 8.7.1 on all 61 of our NetWare servers. This server was
one
of the last servers to be upgraded. The error started occurring about
two
weeks ago before it was upgraded, and the server has been in
production as a
DNS/DHCP server for a few months now.

Ted Tansill
CCNA, CNE, N+