DNS Error

Ibrahim Awwad

unread,

Dec 10, 2002, 2:19:20 AM12/10/02

to

Dear All,

I've changed all our Lan IP Addresses recently. After
that I found some errors on the Primary Domain
Controller. One of these error is DNS Error and it's
being reported to the event log repeatedly. The error is:
"DNS Server has updated its own host (A) records. In
order to insure 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 ActiveDirectory replication partners
do not have the correct IP address(es) for this server,
they will be unable to replicate with it.

To insure proper replication:
1) Find this server's ActiveDirectory 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 ActiveDirectory 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.

Can any one help me!!
For more information, see Help and Support Center at "

Alex Acetozi

unread,

Dec 10, 2002, 3:56:46 AM12/10/02

to

I would say that you may have changed the servers IP
address also and now your DC is trying to replicate with
the other DCs but it cant find them because the old IP
address no longer belongs to the DCs.

Make sure that if you have changed these address also, you
will need to configure replication between your Active
Directories again pointing to the new address.

If you dont have more than one DC, but you do have an
Active Directory integrated Zone, you may ignore it since
you dont need to replicate any information with other DCs.

Alex

>.
>

Ibrahim Awwad

unread,

Dec 10, 2002, 9:36:57 AM12/10/02

to

Dear Alex,
Yes I changed the server IP also. But at the same time
I don't have any other PDCs at our LAN. So the error
still showing up at the Event Log every day. Should I
still ignore it.?

>.
>

Alex Acetozi

unread,

Dec 11, 2002, 3:45:16 AM12/11/02

to

Hi,

Yes, if you dont have any other Domain Controllers in your
network, you should ignore it, since you dont need to
replicate any information.

Alex

>.
>

Amanda

unread,

Dec 18, 2002, 8:18:25 AM12/18/02

to

I recieve the following error in my event logs on my domain controller
periodically. I have checked everything it says to check and all of the
settings are fine. Has anyone else seen this? If so, do you know how to
get rid of it?

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 12/17/2002
Time: 9:04:01 AM
User: N/A
Computer: DC1
Description:
The DNS server encountered a packet addressed to itself -- IP address
10.2.X.X.

The DNS server should never be sending a packet to itself. This situation
usually indicates a configuration error.

Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS
server unless subzone is also on this server.

Example of self-delegation:
-> This DNS server dns1.foo.com is the primary for the zone foo.com.
-> The foo.com zone contains a delegation of bar.foo.com to dns1.foo.com,
(bar.foo.com NS dns1.foo.com)
-> BUT the bar.foo.com zone is NOT on this server.

Note, you should make this delegation check (with nslookup or DNS manager)
both on this DNS server and on the server(s) you delegated the subzone to.
It is possible that the delegation was done correctly, but that the primary
DNS for the subzone, has any incorrect NS record pointing back at this
server. If this incorrect NS record is cached at this server, then the
self-send could result. If found, the subzone DNS server admin should
remove the offending NS record.
Data:

Thanks,
Amanda