Environment: OESNW, sp7, edir 8.8.1, four identical nodes in a
cluster.

DNS is running on the cluster and a secondary DNS server running on a
stand-alone. These were configured as co-primary.

Everything was working fine until a drive failed in the array holding
the DNS cluster volume and the array would not rebuild onto a new
drive. Had to delete and re-create the volume, pool, and virtual NCP
server for the pool.

After the rebuild DNS would still load in the cluster and was
resolving correctly, but the clusterd DNS server could not be managed
in iManager. Attempting to view/modify the DNS server would result in
an incomprehensible error page in iManager. Researching the issue it
appeared that the best course would be to delete and re-create the DNS
server so that all the necessary properties would be correctly written
out to the virtual NCP server.

Did this, with TID3621362 as a reference, waited until all the obits
had cleared before creating the new DNS server, and verified that the
DNIP properties had been created on the virtual NCP server. Now,
attempting to load named.nlm (load named.nlm -s -v APPS4) results in
the following error message:

Jun 18 10:33:34.000 general: main: notice: starting BIND 9.2.0
Jun 18 10:33:34.000 general: dns/db: critical: eDirectory login failed
with error -603
Jun 18 10:33:34.000 general: dns/db: critical: Failed to load RRs of a
zone with error -603
Jun 18 10:33:34.000 general: dns/hints: warning: Loading Root data
from directory Failed
Jun 18 10:33:34.000 general: server: critical: loading configuration:
(result code text not available)
Jun 18 10:33:34.000 general: server: critical: exiting (due to fatal
error)
Jun 18 10:33:36.000 general: main: notice: exiting

I have re-run the process and still get this error every time I
attempt to load named.nlm. Any suggestions to resolve this and get
named.nlm loading again?

Thanks,

DeVern