Replacing a Missing DNS Locator Object

The DNS server shows the following error in /var/opt/novell/log/named/named.run:

general: dns/db: critical: Unable to read locator reference from NCP server

Running /etc/init.d/novell-named status briefly shows:

rndc: connect failed: 127.0.0.1#953: connection refused

NOTE: When a DNS locator object is deleted, the DNS server will continue to function properly, until the server is rebooted. You can even /etc/init.d/novell-named restart and still have the server function properly with a missing DNS locator object. However, DNS services will fail after a server reboot with a missing locator object.

You will need to recreate the missing DNS locator object. However, you should first check to see if there are any pre-existing objects elsewhere in the tree. Use ldapsearch to look for all DNS locator objects. If no DNS locator objects are found, your ldapsearch will look like the following:

dnsdhcp:~ # ldapsearch -x -b "" objectClass=dNIPlocator
# extended LDIF
#
# LDAPv3
# base <> with scope subtree
# filter: objectClass=dNIPlocator
# requesting: ALL
#

# search result
search: 2
result: 0 Success

# numResponses: 1

Please call Novell Technical Services if you find a DNS locator object elsewhere in the tree, or multiple DNS locator objects.

Steps to Recreate the DNS Locator Object

1. Open YaST2, select Open Enterprise Server, then OES Install and Configuration
2. No changes are needed in the Software Management screen, just click Accept
3. Change the Novell DNS Services to enabled in the Novell Open Enterprise Server Configuration screen.
4. Select the Novell DNS Services link
5. Type admin's password
6. Make sure the information is correct in the Novell DNS Configuration screen, then select Next.
7. There is no need to create a new DNS Server Object, just select Next.
8. Select Next at the Novell Open Enterprise Server Configuration screen
9. Select Finish when you reach Installation Completed.
10. Select Configure Later, then Next, and quit YaST2.
11. Restart the Novell DNS service: /etc/init.d/novell-named restart

You may also cross reference How to recover corrupt DNS and DHCP, TID7002316. Although this TID was written for Novell DNS on Netware, the principles still apply to OES Linux.

When a supportconfig looks for the DNS locator object, it only looks in CONFIG_DNS_LOCATOR_CONTEXT specified in the /etc/sysconfig/novell/NvlDns* file. Supportconfig avoids running root level LDAP queries against eDirectory. However, the Novell DNS daemon (novell-named) itself looks for information directly from eDirectory. If the information the sysconfig file does not match eDirectory, then supportconfig will not find the object, even though DNS services is functioning properly. This mismatch is rare since the administrator has no need to change the configuration file. Only YaST uses the sysconfig file, not novell-named.