For us, the fix was to set the reverse lookup zone to allow both secure and non-secured updates.
This problem cropped up when we were setting up a disjoined namespace, so as computers were migrated from one domain to the other, they no longer had rights to update the reverse lookup zone.
In my case, there was another system with the IP address of the actual system in the reverse DNS. After removing the entry from the reverse DNS, I got rid of the message.
In my case, I added the computer account to have full rights to the DNS record of the server. The event, however, did not clear until I added the computer account (full rights) on the Reverse DNS entry as well.
This error occurs when the server is trying to update the DNS information and does not have enough privileges.
On the entry in the forward lookup zone make sure that %DOMAIN%\%COMPUTERNAME%$ has the following (special) permissions:
* Write all properties
* Read permissions
* All validated writes
On the entry in the reverse lookup zone make sure that %DOMAIN%\%COMPUTERNAME%$ has full control.
I ran into this when I had a server that was a member server of a domain on a different subnet, but the DC DNS servers did not have a Reverse Lookup Zone for the subnet in which the member server was. I added a reverse lookup zone for the subnet that the member server was in, and the error went away (as the server was now able to register its PTR record).
In my case, i deleted the old entry in the reverse lookup zone (i had changed the server name, the old one was not deleted on dns server). After deleting, ipconfig /registerdns works fine without an error in the event log.
This can happen if you have the "Register this connection's address in DNS" option selected. Go to your network connection's advanced properties, then go to the DNS tab, and the check box is at the bottom. The problem happens when the above network connection is your Internet connection. You do not have rights to update your ISP's DNS servers. Uncheck the box for the error message to go away.