Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2690
  • Last Modified:

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

0
Wibble_
Asked:
Wibble_
1 Solution
 
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
 
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

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now