Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNS error in event viewer

Status
Not open for further replies.

Pipeops

MIS
Apr 28, 2008
77
US
I have been receiving this error in one of my domain controllers. The IP address is a domain controller and the DNS name is a printer. Does anyone have a clue of what steps i should take? I do not want to screw up my DNS server.

Thanks,

-I


The error:

The DNS server encountered a packet addressed to itself on IP address --.--.--.--. The packet is for the DNS name "------.---.--.--.---.". 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.

For more information, see Help and Support Center at
 
I did everything i could here but no luck. I had to dash out the ip address for security purposes as well as the DNS name of the printer. The event error in the dns.log file is this:

20080519 21:35:43 C94 ANY DNS server detected send to self at IP --.--.--.-- - message follows:
20080519 21:35:43 C94 PACKET UDP Snd --.--.--.--(DC IP address) 2b75 Q [0000 NOERROR] (11)name(2)name(4)name(4)name(3)name(0) <------DNS NAME OF THE PRINTER
 
Did you check all the NS records and delegations of the printer name subdomains?
 
Part of the original solution was to check those and it all seemed normal. This issue started once the printer was installed over at a remote location in Chicago. Is it possible that the actual printer is malfunctioning? Or is it still the DNS issue since the DC sends out a packet for its own IP address?
 
Thanks for your help. The problem was in one of the NS records in the subzone.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top