EventID 11202 from DnsApi (The system registered host (A) resource records for a network adapter with these settings...) is one of the events listed under DNS Client Registration on http://technet.microsoft.com/en-us/library/cc735718.aspx, dated November 13, 2007.When a host resource record registration succeeds, I have not seen this event in the System log. How to make it appear?Background:When a host resource record registration fails, DnsApi Warning Event ID 1164 (The system failed to register host (A) resource records for the network adapter with these settings...) does appear in the System log.On the idea that the absence of EventID 11202 was due to a default that suppressed Information events from the DHCP Client service, which handles DNS dynamic updates, I added a REG_DWORD 0x4 to MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp\Parameters to allow Information events, but that didn't make any difference.The appearance of EventID 11202 would be useful when troubleshooting DNS dynamic updates because it provides a quick way of knowing that you solved the problem.

Hi, These events are generated in the DNS server. The following article has introduced how to access the logs. http://technet.microsoft.com/en-us/library/cc786376.aspx Hope it helps.Arthur Xie - MSFT

Thanks for your reply. I checked the DNS Server log, and found no instances of EventID 11202, or any events whose source is DnsApi.I hope I am not missing something, but it seems like EventID 11202, as well as otherevents whose source is DnsApi,is a client-side event, andwould appear inon theDNS client, not the DNS Server.So my question remains, how to get EventID 11202 to appear when it should?

Hi, Yes, you are right. The DNS Client Event Logs are generated in DNS client computers. We could find it in Windows Logs/System. You may specially search events whose source is DnsApi. If you still do not find any event 11202, run "ipconfig /registerdns" in command prompt and check if there is any event from DnsApi.Arthur Xie - MSFT

Thanks again for replying.I ran ipconfig /registerdns. The System log shows events from DnsApi associated with registration failures (such as Event ID 11164), but it does not show events associated with registration success (such as Event ID 11202).I would not even know about the events associated with registration success, except I found them listed at http://technet.microsoft.com/en-us/library/cc735718.aspx when I was researching registration failure. The fact that registration success events are listed made me want to know why they were not appearing in the System log.

Hi Sejong, With the event ID, we could find the reason in the article: Either the DNS server does not support the DNS dynamic update protocol or the authoritative zone for the specified DNS domain name does not accept dynamic updates. To register the DNS host (A) resource records using the specific DNS domain name and IP addresses for this adapter, contact your network administrator. This may be caused by some settings on your DNS server. If your DNS server is built in Windows Server 2003/2008, I suggest that you post in our Windows Server forum for discussions. http://social.technet.microsoft.com/Forums/en-US/winserverNIS/threads/Arthur Xie - MSFT

I apologize for not being clear enough. I hope the following is clearer:When I purposely set an incorrect DNS server IP address on the client computer, and then ran ipconfig /registerdns, registration failure events such as 11164 appeared in the System log.When I set a correct DNS server IP address on the client computer, and then ran ipconfig /registerdns, no registration success events such as 11202 appeared in the System log, even though the DNS registration of the client computer had been successful when viewed from the DNS server.Since both registration failure and registration success events are listed in the TechNet article I referenced in my first post, I expected that both registration failure and registration success events would appear in the System log as appropriate for the condition.

Hi, Yes, if the computer is registered in the DNS server properly, the DNS server would send feedback to the client and event 11202 will be logged. However, in your client, event 11202 is not logged. I suspect that mistakes may exist in the DNS server. Although the client connect to the DNS, the server may not register the client computer properly. Therefore, I suggest that you contact our Windows server support and try to find if there is anything we need to do on the DNS server to resolve this issue.Arthur Xie - MSFT

I had the same issue 2 days ago. I've just create a reverse lookup zone for the subnet which belong the client.After this the warning stoped.