W2K DNS error

[bdj]

I have a W2k Advanced server with cashing DNS. I keep getting this error:


Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 11/19/2003
Time: 10:36:44 PM
User: N/A
Computer: JDBW2K
Description:
The DNS server encountered a packet addressed to itself -- IP address 172.20.2.1.

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:
0000: 50 25 00 00 P%..

Any ideas on what may be happening, and or how to stop this. I am not familiar with setting up DNS.

Thanks.

bdj

[Bill in SD, CA]

Don't know if this will help or not but .....

In Network and Dialup Connections check the properties for TCP/IP.

Ensure that:

Obtain an IP address and obtain a DNS server address are ticked.

In Advanced this is what I have ticked under DNS:

Append primary and connection specific DNS suffixes.
Append parent suffixes of the primary DNS suffix.
Register this connection's addresses in DNS

You also might try un-installing TCP/IP, re-boot, re-install TCP/IP, and re-boot.
Something may have corrupted a file.

Bill

[DVNT1]

some relating info http://www.eventid.net/display.asp?eventid=7062&source=

[bdj]

Thanks guys for the responses. I haven't had time to try and check them out, I've been busy installing new systems in two of our offices.

bdj