Event ID 11163 Source DnsApi
| Event ID | 11163 |
| Source | DnsApi |
| Type | Warning |
| Description | The system failed to register host (A) resource records (RRs) for network adapter with settings: Adapter Name : {02C23FBC-7048-4752-89FA-2ADAD732F5D4} Host Name : SERVICE Primary Domain Suffix : bbc.local DNS server list : 192.168.16.2 Sent update to server : 192.1.1.1 IP Address(es) : 192.168.16.48 The reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress. 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. |
| English, please! | Request a translation of the event description in plain English. |
| Concepts to understand |
What is the role of a DNS server? What types of resource records are recorded in DNS? |
| Comments |
Anonymous
This problem can also occur on machines which have been cloned. This will result in the machine`s A PTR record being unreadable/writeable by the relevant machine. As per Brian Collins' comment, check the permissions for the A record are not owned by the wrong machine or a deleted account (characterised by unknown SID message). Brian Collins On a machine here, we tried "ipconfig /registerdns" and it did not work. We changed the zone updates to “unsecure and secure” and while that worked, I did not want to have to live with it. Eventually, what worked was un-joining the machine from the domain, deleting the disabled computer account, and re-joining the computer to the domain. What tipped us to this was that the A- and PTR- records had an unidentified SID listed in the security tab. That should have been the AD name. After un-joining and re-joining, the AD name was listed instead of just the SID. D. Wilson I found this problem could also manifest itself when the time on the client is uncoordinated. On my machine, I had this problem and my client clock was 12 hours behind. I reset the clock, rebooted, and the problem was fixed. R. Crowley I had this problem after re-installing an XP Pro machine. Renewing the IP address did not resolve the problem, nor did “ipconfig /registerdns”. I resolved this by first removing the host (A) and pointer (PTR) records from DNS and then running “ipconfig /registerdns”. D. Zoelfl On a Windows XP client, create the following registry entry “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters” Key: UpdateSecurityLevel. Type: REG_DWORD. Value:0x00000100. Set the Value to 0x00000100 to use secure dynamic update only. This parameter can be used to control the security that is used for DNS dynamic updates. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! HairyMonster This can be fixed by releasing then renewing the DHCP address, which forces a correct update to the DNS records. ipconfig /registerdns does not work in solving this issue. |
| Search | Google Web - Microsoft Support - Bing - EventID.Net Queue - More links... |
| Feedback | Send comments - Notify me when updated |
| Print version |