Question : Event ID 7062

Not sure why I am getting this all of a sudden.  Just started 9/6/09, installed some windows updates that day as well.  Recorded in dns event viewer every 1 hour.

excerpt from the debug file:

20090914 11:25:27 914 PACKET  022C3AE0 UDP Snd 198.x.x.x    333f   Q [0001   D   NOERROR] PTR   (3)194(2)x(3)x(2)x(7)IN-ADDR(4)ARPA(0)

20090914 11:25:27 914 ANY     Packet at 022C3AE0 is detected as being sent to DNS server itself at IP 198.x.x.x - message follows:

20090914 11:25:27 914 EVENT   The DNS server encountered a packet addressed to itself on IP address 198.x.x.x.
The packet is for the DNS name "194.x.x.x.IN-ADDR.ARPA.". The packet will be discarded.
This condition 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.

  5) Root hints.



Example of self-delegation:

  -> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com.

  -> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com,

  (bar.example.microsoft.com NS dns1.example.microsoft.com)

  -> BUT the bar.example.microsoft.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.



You can use the DNS server debug logging facility to track down the cause of this problem.

I checked my forwarders and dns domains says "all domains" and the forwarder IP's are the 2 provided by my ISP.  This is the only domain on our network.

Not sure why this would configured as it is, but the IP of the teamed nics has 10.9.x.x and 198.x.x.x, odd but it has been working fine until 9/6/09 when the warnings started appearing.

Ideas?

Answer : Event ID 7062

I think this is probably part of your problem.

Give it a proper IP make sure it is configured for an internal DNS server.

You may need to reboot as lots of services will be tied to this.