Event ID - 11160

Event Id11160
SourceDnsApi
DescriptionThe system failed to register pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name: {CF832F65-C322-48F9-B4D3-4F3A643BA4D4} Host Name: Adapter-specific Domain Suffix: DNS server list: Sent update to server: IP Address: 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.
Event InformationThis may occur when a client trying for a dynamic DNS registration to a server which is not supporting it.To resolve this issue you have to disable dynamic DNS registration feature in client system. To do this follow the steps given below.
1) Open properties of local area connection.
2) Select TCP/Ip properties. Click on Advanced lab.
3) Click on DNS tab, uncheck "Register this connections address in DNS.

This information from some newsgroups may help you:
------------------------------------------------------------------------------
1. Analyzed MPS reports taken from both domain controllers in the domain and the Exchange 2003 server.
2. All looked clean except for a couple obsolete domain A records for a domain controller that was no longer in the domain.
3. Deleted the obsolete domain A records for the domain controller that no longer existed.
4. Also removed DNS from a secondary DC (which the customer did not want it to be a DNS server any longer).
5. After the above actions, the missing PTR records populated.
6. The Event IDs 2012 and 2013 are no longer occurring in the System Log of the Exchange 2003 server. 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. 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.
Register this connections address in DNS" option selected. Go to your network connections advanced properties, then go to the DNS tab, and the check box is at the bottom.
Reference LinksHow To Promote a Member Server Running IIS to a Domain Controller Running IIS

More Information

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.