Monday, October 13, 2008

Windows Dynamic DNS Not Updating Client IPs

Machines do not update their IP addresses on Windows 2003 Dyanamic DNS.


Machine SID has changed and can not update the DNS record. Go into dns and delete the entry for the machine. The machine will automatically register with the correct IP address.

Visual /Learning:

I found some information that helped me here:

----- Text from link to ------
Troubleshooting a PC today, that had numerous DnsApi errors in the System event log. The WinXP client was unable to update its host record on the DNS server. The whole error message is listed below. The error was caused by a host record security problem. Our DNS is Active Directory integrated. We allow only secure updates. When a client boots up, gets an IP via DHCP, it then sends a request to the DNS server to create a host record. The reason why it fails, is because the host record already exists, but the WinXP client doesn't have permissions to change it. This particular machine had been imaged recently, and after running sysprep, the machines old domain account was deleted, and a new one was created with a different SID. When I open the DNS console, then the machine's host record, on the security tab was one of those ? {1-5-512-5464} type SID entries, that you commonly see on a security tab in Windows, when the account no longer exists. Well, in this case, it was a computer account, not a user account. After I deleted the host record and reverse-lookup records, I rebooted the client and no more errors in the System event log. Of course, you can also use the ipconfig /registerdns command and get the same results. Note that in the error message below, there is a line that says "Sent update to server:", which I thought was important, but its not, its just a red herring. I have no idea why it says that, but that is not the root of the error.
*************************************************************WarningSource: Dns
ApiEvent ID: 11163
Event Time: 5/23/2006 9:00:44 AM
User: n/a
Computer: Somecomputer
The system failed to register host (A) resource records (RRs) for network adapter with settings:
Adapter Name : {28442B0F-5CC5-4833-B293-823C9FF43614}
Host Name : somecomputer
Primary Domain Suffix : Domain.local
DNS server list :,
Sent update to server :
IP Address(es) :

The reason the system could not register these RRs was because theDNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this updaterequest 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.*****************************************************
------- End Of TEXT from Link ------------

No comments: