Article ID: 235689 - View products that this article applies to.
This article was previously published under Q235689
This article describes how to troubleshoot the cause or causes of event ID 7062 on a DNS server that is running Microsoft Windows 2000 or Microsoft Windows NT Server 4.0.
If event ID 7062 logs on your DNS server, it will appear as follows:
As part of your troubleshooting, you may find that none of the steps that are listed in event ID 7062 apply to your DNS server. However, event ID 7062 may continue to log on your DNS server. This article discusses some of the other reasons why this issue may occur.
EVENT message 7062:
DNS Server encountered a packet addressed to itself -- IP address<actual IP address>. 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.
Step 4 of event ID 7062 may lead you to conclude that for the event to be triggered, a primary DNS server must create a delegation of a subdomain. However, the root DNS servers maintain the .com, .net, and other domains. Additionally, the root DNS servers delegate the namespace under those domains to other DNS servers. Therefore, although your DNS server may be the primary DNS server for example.com, your DNS server has been delegated that responsibility by the ".com" DNS server or servers.
This means that if you have registered a domain with the NSFnet Network Information Center (InterNIC), and they delegate that domain to your DNS server, it is your responsibility to make sure that your DNS server can handle all requests for the registered domain.
For example, you have a DNS server at dns.example.com, and you have recently registered example.org with InterNIC. After InterNIC delegates example.org to your DNS server, you must create a zone file that can answer queries for example.org.
The following hypothetical sequence of events describes how event ID 7062 may continue to log to your DNS server if you have not configured it to maintain zone files for domains that you have registered.
How to find the actual requested domainsTo find the actual requested domains, you must debug your DNS server. After you have created a log file, open it in Microsoft Word or Microsoft Excel. We do not recommend that you open the file in Notepad because Notepad does not parse characters into an easily readable format.
When you have the log file open, search for "7062." This search should bring you to the first error. After you find the error, scroll up. A DNS query log looks similar to the following code.
The following describes what occurs during the important phases of this log:
dns_ProcessMessage() for packet at 00A5E524. dns_AnswerQuestion() for packet at 00A5E524. Node for (3)www(10)mycompany(3)com(0) NOT in database. Closest node found"com." Encountered non-authoritative node with no matching RRs. dns_ProcessMessage() for packet at 00A5EAC4. Processing response packet at 00A5EAC4. Packet contains RR for authoritative zone node: "dns.hello.com." -- ignoring RR.dns_ContinueCurrentLookup() for query at 00A5E524. dns_AnswerQuestion() for packet at 00A5E524. dns_AnswerQuestionFromDatabase() for query at 00A5E524 node label = www question type = 0x0001 ERROR: Self-send to address 10.1.1.1!!! Log EVENT message 7062 (80001B96):
Event ID 7062 logs even when zone transfers are disabledImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Event ID 7062 will log even if zone transfers are disabled if the Notify option has been configured to notify a DNS server or servers that are listed on the Name Servers tab.
By default, a Windows 2000-based primary DNS server that has multiple zones is configured to notify the servers that are listed on the Name Servers tab.
Note Disabling zone transfers does not disable the Notify option. If the Notify option is set to notify a DNS server or servers that are listed on the Name Servers tab, it will continue to do this.
To disable zone transfers, follow these steps:
For more information, see the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/218814/ )DNS server encountered a packet addressed to itself
Article ID: 235689 - Last Review: February 26, 2007 - Revision: 3.3