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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNS error 7062

Status
Not open for further replies.

rrdavis07

MIS
Jun 2, 2004
88
US
I've read quite a bit about this error, but can't seem to come to a resolution.

Here is the event log entry:

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 8/3/2006
Time: 10:18:49 AM
User: N/A
Computer: USD360-TYAN
Description:
The DNS server encountered a packet addressed to itself on IP address 192.168.168.6. The packet is for the DNS name "_ldap._tcp.dc._msdcs.usd360.". 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 Data:
0000: 50 25 00 00 P%..

I've checked the Root Hints in Cache.dns and didn't see anything that looked like it should be there. There were no entries pointing to the local DNS Server, which I believe is correct.

How else to I go about correcting this event. I'm getting several dozen of these daily and they are filling up my event viewer.


Randy Davis, MCP
Southwind Technology Solutions
 
Still having issues with this one. Thought I'd bump it back to the top and see if anyone has any thought. Thanks for your help.

Randy Davis, MCP
Southwind Technology Solutions

 
Sounds like DNS configuration issue. This search result may help,

Event ID Troubleshooting
Event ID 7062: DNS Server encountered a packet addressed to itself · Event ID 7200 - Background thread FDoUpdateCatalog halted on database "First Storage ...


Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top