DNS server attempting to update its own record

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have a domain controller, DC1, with two NICs, one of which is currently
unused and disabled. At some point in this server's life, the second NIC was
enabled, and plugged into the network, where it received a DHCP address.

Ever since then, I've had two A records for DC1, the correct record
(10.1.1.10), and the record for the DHCP address (10.5.0.102). I'm getting a
regular number of DNS 6702 errors in the event log (see below). I've tried
manually deleting the record, but it always comes back.

How can I get this invalid A record to go away?

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date: 3/18/2005
Time: 10:15:51 AM
User: N/A
Computer: DC1
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: 2d 23 00 00 -#..
 
In
William Albert said:
We have a domain controller, DC1, with two NICs, one of
which is currently unused and disabled. At some point in
this server's life, the second NIC was enabled, and
plugged into the network, where it received a DHCP
address.

Ever since then, I've had two A records for DC1, the
correct record (10.1.1.10), and the record for the DHCP
address (10.5.0.102). I'm getting a regular number of DNS
6702 errors in the event log (see below). I've tried
manually deleting the record, but it always comes back.

How can I get this invalid A record to go away?

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date: 3/18/2005
Time: 10:15:51 AM
User: N/A
Computer: DC1
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: 2d 23 00 00 -#..
Click to expand...

In the DNS management console, interfaces tab, do you have DNS listening on
10.1.1.10 only?
 
Kevin D. Goodknecht Sr. said:
In

In the DNS management console, interfaces tab, do you have DNS listening on
10.1.1.10 only?
Click to expand...

No, it was listening on all IP addresses. I took out the 10.5 address, and
upon applying the settings, the invalid A record is no longer there.

Thanks for the help!
 
Back
Top