Event 7062 - DNS server encountered a packet addressed to itself

  • Thread starter Thread starter al harris
  • Start date Start date
A

al harris

DNS Server encountered a packet addresses to itself -- IP address w.x.y.z.
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 server 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 DNS server

Example: -> This DNS server dns1.microsoft.com is the primary for the zone
microsoft.com. -> You have delegated the zone bar.microsoft.com to
bardns.bar.microsoft.com and are NOT running the bar.microsoft.com zone on
this DNS (dns1.microsoft.com). Note, you should make this check (with
nslookup of 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.

Tried the fix in the message but that did not help, any suggestion?
My DNS environment includes:
3 dns servers (all AD integrated)
1 domain
Many reverse zones
No access to the internet
 
In
al harris said:
DNS Server encountered a packet addresses to itself -- IP address
w.x.y.z. 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 server 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 DNS server

Example: -> This DNS server dns1.microsoft.com is the primary for the
zone microsoft.com. -> You have delegated the zone bar.microsoft.com
to bardns.bar.microsoft.com and are NOT running the bar.microsoft.com
zone on this DNS (dns1.microsoft.com). Note, you should make this
check (with nslookup of 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.

Tried the fix in the message but that did not help, any suggestion?
My DNS environment includes:
3 dns servers (all AD integrated)
1 domain
Many reverse zones
No access to the internet
Click to expand...

Configuring a forwarder usually eliminates this error.

300202 - HOW TO Configure DNS for Internet Access in Windows Server 2000 :
http://support.microsoft.com/?id=300202

If that doesn;t work, please provide additional info such as an ipconfig
/all of the server, if you have AD running, etc.

--
Regards,
Ace

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Infinite Diversities in Infinite Combinations.
=================================
 
That did not help, still having the same problem. My network has 'no
internet access' do I need a root server? If not, what steps do I need to
take to ensure proper configuration on my 3 dns server?

Thanks
 
In
al harris said:
That did not help, still having the same problem. My network has 'no
internet access' do I need a root server? If not, what steps do I
need to take to ensure proper configuration on my 3 dns server?
Click to expand...

Were you able to actually configure a forwarder, or was the option grayed
out?

Are you saying you have no Internet access whatsover? Do you use a Proxy or
ISA server?

Is this error appearing on all three of your DNS servers? Are these all DCs
too?

Are any of these servers multihomed (multiple NICs)?

Can you post an ipconfig /all of all three your DC/DNS servers please?

Ace
 
Back
Top