Click Here to Install Silverlight*
United StatesChange|All Microsoft Sites
Microsoft TechNet
|TechCenters|Downloads|TechNet Program|Subscriptions|Security Bulletins|Archive
Search for
Details
Product:Windows Operating System
Event ID:6702
Source:DNS
Version:5.2
Symbolic Name:DNS_EVENT_UPDATE_DS_PEERS_FAILURE
Message:DNS server has updated its own host (A) records. In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.

If this DNS server's Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it.

To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact. (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.
   
Explanation

Active Directory clients use DNS to locate domain controllers for administration and logon. A domain controller usually points to itself for DNS. When there are additional domain controllers in the domain, they must point to the first domain controller (called the DNS server in this message) that was installed in the domain and then to themselves as secondary. This server could not register its dynamically updated locator records with DNS on any other domain controller in its directory service (DS) forest.

Possible causes include:

  • There are no other domain controllers.
  • The other domain controllers in this forest do not have the correct IP address for this server.
   
User Action

If there are no other domain controllers in this forest, no user action is required.

If there are other domain controllers that are Active Directory replication partners in this forest, enable replication by ensuring that at least one correct DNS record is registered on each domain controller.

To ensure that a correct DNS record is registered on each domain controller

  • Find this server's Active Directory replication partners that run DNS.
  • Open DNSManager and connect in turn to each of these replication partners.
  • Find the host (A) resource record registration for this server on each of the other replication partner domain controllers.
  • Delete those host (A) records that do not have IP addresses corresponding to any of this server's IP addresses.
  • If a domain controller has no host (A) records for this server, add at least one that corresponds to an IP address on this server. (If there are multiple IP addresses for this server, add at least one that is on the same network as the domain controller you are updating.)

It is not necessary to update every replication partner. It is only necessary that the host (A) records be working on enough replication partners so that every domain controller that replicates with this server receives new data through replication.

For more information about DNS and DNS troubleshooting procedures, see Domain Name System(DNS)Center.

© 2009 Microsoft Corporation. All rights reserved. Contact Us |Terms of Use |Trademarks |Privacy Statement
Microsoft