Event ID 6702

	Home \| Site Map \| How To \| Windows Vista \| Case Studies \| Articles \| Forums \| Services \| Donations \| Careers \| About Us \| Contact Us\|

Event ID 6702 - DNS server has updated its own host (A) records

Symptom: You Windows DNS server Event Viewer receive Event ID 6701 with the following 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.

Actions: except above mentioned 6 actions, you may the following suggestions.

If you have just one domain controller as DNS server, make sure the DC points itself for DNS - Case Study.
If you have two or more DNS servers, each DNS server should point other DNS as primary DNS and itself as the secondary.
If you have two or DNS servers, make sure they can talk to each other.
If the DNS is multihomed computer and RRAS server, make sure the computer registers only one A record on the DNS - Case Study.
This also can be due to using an ISP’s DNS in the DNS server IP properties. You can get rid of this by installing an internal DNS and using the DNS forwarders - Case Study.