Problem : The system failed to register pointer (PTR) resource records (RRs) for network adapter with settings

Problem : The system failed to register pointer (PTR) resource records (RRs) for network adapter with settings

The following event appears exactly every 24 hours on one of our servers
This server is a domain member already and is working OK

Server OS is Windows server 2003 , Domain is based on Windows server 2003 as well
The following is a capture of the exact error message as it shows in the event viewer:

Event Type:      Information
Event Source:      DnsApi
Event Category:      None
Event ID:      11160
Date:            25-Sep-09
Time:            10:08:44 PM
User:            N/A
Computer:      MAIL-01
Description:
The system failed to register pointer (PTR) resource records (RRs) for network adapter
with settings:

Adapter Name : {357970E8-A46D-48D0-A068-696CDD521B95}
Host Name : *******
Adapter-specific Domain Suffix : **********.LOCAL
DNS server list :
192.168.1.10, 192.168.1.11
Sent update to server : 192.168.1.10
IP Address : 192.168.1.13

The reason that the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.

You can manually retry DNS registration of the network adapter and its settings by typing “ipconfig /registerdns” at the command prompt. If problems still persist, contact your DNS server or network systems administrator.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 38 23 00 00               8#..

Regards


Solution: The system failed to register pointer (PTR) resource records (RRs) for network adapter with settings

Check if there’s a pointer record for 192.168.1.13 in your reverse lookup zone for 192.168.1.0.
If so, delete it, wait until the deletion has replicated to the other DNS server, then open a command prompt on the server in question, and enter
ipconfig /registerdns