DNS error eventid 7062

[Eric Foreman]

I keep getting this error on my server. It is an Win2k AD DC running AD
integrated DNS. It is the only one DNS server and the only server on the
network.

Thanks.

DNS Server encountered a packet addresses to itself -- IP address
<192.168.1.199>. 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.

Here is my ipconfig from the server.


Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : hostname
Primary DNS Suffix . . . . . . . : primary.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : primary.com

Ethernet adapter Intel Pro 1000 MT Gigabit Ethernet Adapter - onboard:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connect
ion
Physical Address. . . . . . . . . : 00-C0-9E-27-57-32
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.199
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.2
DNS Servers . . . . . . . . . . . : 192.168.1.199

 

[Deji Akomolafe]

I assume you've checked these:
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.

If yes, what did you find?

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon

 

[Eric Foreman]

There are no secondary zones, forwarders are our ISP. No errors there.

 

[åÍÅÌØÑÎÅÎËÏ æ£ÄÏÒ]

I had such problem when there was a reverse lookup zone on the root DNS
server. To solve it I had deleted root zone. When I stopped reverse lookup
zone the event stopped log too.