Our forums are currently in maintenance mode and the ability to post is disabled. We will be back up and running as soon as possible. Thanks for your patience!



Event ID 6702

By jorgerodriguezhn ·
Hi, I have a Single DC Server and no other DS-integrated peer DNS server is defined. In the same server where i Have the Active Directory, I have the DNS server. so i can't stop this event id 6702 coming in the DNS event log, and its a Error. I know that in the message says that I should ignore these error, but me and my boss wna to know why it won't stop coming.

I have search several internet pages, and all says that I should check the IP address, the dns replicator, but I don't have any. so can you guide what should I do?

this is the 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.

For more information, see Help and Support Center at

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Same issue

by d3vlabs In reply to Event ID 6702

I have that "problem" on my network as well and and this network had 2 DC's at some point in time so chances are there are still some info left from the 2nd DC. Still looking for a way to resolved this. Anyone?>

Related Discussions

Related Forums