MS DNS Error

Paul T Laudenslager ( (no email) )
Fri, 13 Nov 1998 15:27:33 -0500

I'm having an error show up in the event viewer regarding my DNS server. I
have my domain, "virginia.com", as well as approx 32 others (most of which
are on a shared ip of 4.21.72.140) running on a NT4AS-sp4 system. I setup
all of my customers pretty much the same way and I've been unable to track
down the error. You may use nslookup, but I'm not sure where to look to
find the error.

Thanks in advance for your time and consideration.
Paul & Susan Laudenslager
paul@virginia.com
susan@virginia.com

The error is as follows...

DNS Server encountered a packet addressed to itself -- IP address
4.21.72.130.
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 DNS server Example: -> This DNS
server dns1.foo.com is the primary for the zone foo.com. -> You have
delegated the zone bar.foo.com to bardns.bar.foo.com. and are NOT
running the bar.foo.com zone on this DNS (dns1.foo.com). -> bar.foo.com
MUST NOT have an NS record that points at dns1.foo.com. Note, you
should make this 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.