Environment
NetWare 6.x DHCP
Situation
Primary DNS servers for the forward and reverse (in-addr.arpa) lookup zones were different.
Dynamic DNS is not being updated. On the Primary DNS server of the forward lookup zone, the following error is seen on the DNS Server screen:
error: Client x.x.x/x#15276: updating zone 'x.x.IN-ADDR.ARPA/IN' :Novell DDNS : Not authoritative for update Reverse zone
On the Primary DNS server for the reverse lookup zone the following error was seen on the system console:
Cannod add FQDN: some.name.com with address: x.x.x.x.x to DNS server.
Dynamic DNS is not being updated. On the Primary DNS server of the forward lookup zone, the following error is seen on the DNS Server screen:
error: Client x.x.x/x#15276: updating zone 'x.x.IN-ADDR.ARPA/IN' :Novell DDNS : Not authoritative for update Reverse zone
On the Primary DNS server for the reverse lookup zone the following error was seen on the system console:
Cannod add FQDN: some.name.com with address: x.x.x.x.x to DNS server.
Resolution
The Primary DNS server of the reverse lookup zone must be the same as that of the forward lookup zone. In the NDS/DHCP Console -> DNS tab, click on the forward lookup zone object. On the right, identify the assigned Primary DNS server. Click on the reverse lookup zone and check that it is the same. If not, change it to match.