The DNS Server log on your Windows Server 2003 domain controller records:
Event Type: Error
Event Source:DNS
Event Category: None
Event ID: 6702
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
http://go.microsoft.com/fwlink/events.asp. Data: 0000: 0000267c
NOTE: You can safely ignore this Event ID 6702 error.
This behavior will occur if the domain name is single-label (no suffix, like Local), the domain name zone is Active Directory integrated, and the domain name zone is hosted by two or more domains controllers or DNS servers, because queries for <DomainName>.<DomainName> that are sent from the DNS server to a single-label domain name fail because the zone does not exist.
To workaround this behavior, add the <DomainName>.<DomainName> zone to the DNS server. See How do I create a new zone on a DNS server in Windows Server 2003?
NOTE: See the following tips:
DNS event messages 1 through 1614 in Windows Server 2003.
DNS event messages 1616 through 6702 in Windows Server 2003.
