Share via

DNS 6702

  • Article

Working with my customer today on a funny little error that keeps reappearing in their DNS Logs

Event Type: Error

Event Source: DNS

Event Category: None

Event ID: 6702

Date: XX/XX/XX

Time:               

User: N/A

Computer: ABC123

Description:

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 https://go.microsoft.com/fwlink/events.asp.

 

The server was a Domain Controller running Active Directory Integrated DNS. The namespace it was Authoritative  for was NOT a single label domain, which has been known to cause this error in the past. The solution for that by the way was the following https://support.microsoft.com/kb/914050

In this instance the issue was being cause by teamed NICS….see below;

NIC Teaming creates a virtual adapter for the operating system to use. When looking
through the registry, the
Hkey_Local_Machine\System\CurrentControlSet\Services\TCPIP\Interfaces will show at
least 3 interfaces, 2 for the actual physical cards, and 1 for the virtual card.
After adding the key "DisableDynamicUpdate" and setting it to 1 on each physical
interface in the registry (but NOT the virtual interface), the 6702 errors
stopped.

This solution worked for me.

Comments

  • Anonymous
    July 02, 2015
    The comment has been removed