Clients not updating DNS, trying to send updates to 10.1.1.1

XP clients are unable to update DNS (see event log message below for an e.g.)

This is AD integrated DNS.

10.1.1.1 is not a valid DNS server, or even a valid IP on our domain, I can't find any record of it anywhere

A quick google suggests that XP occasionally decides to use it of it's own accord, but makes no mention of how to resolve the issue.

The DHCP server's (the PDC) IPV4 namserver config only includes the IP's of other domain controllers.

I'm confused :-(

Please help!
Event Type:	Warning
Event Source:	DnsApi
Event Category:	None
Event ID:	11163
Date:		03/11/2008
Time:		19:18:54
User:		N/A
Computer:	A-A04
Description:
The system failed to register host (A) resource records (RRs) for network adapter
with settings:
 
   Adapter Name : {654BFF58-E14A-4C72-9F00-XXXXXXXXXXXX}
   Host Name : a-a04
   Primary Domain Suffix : xxxx.local
   DNS server list :
     	10.10.0.1, 10.10.0.26, 10.10.0.22
   Sent update to server : 10.1.1.1
   IP Address(es) :
     172.16.1.230
 
 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.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

Wibble_Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

loknaCommented:

I would try the following:
Remove the PTR and A records from the DNS server and run ipdonfig/registerdns on the clients. You can do this in DNS admin on the server.
 
If that doesnt work, try this:
Remove the computer from the domain completely (workgroup mode)
Delete the associated computer account from active directory if it still exists
Enrol the computer back into the domain.
 
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
torimarCommented:
Please check the solution posted in this EE thread:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_21867677.html

If you are interested in a very in-depth discussion about the issue, consider studying this thread:
http://forums.techarena.in/server-dns/439542.htm
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.