DNS problem

Posted on 2011-10-09
Last Modified: 2012-05-12
hi ,

After migration i am facing this issue

Event Type:        Warning
Event Source:    DNS
Event Category:                None
Event ID:              7062
Date:                     10/10/2011
Time:                     7:38:19 AM
User:                     N/A
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 is the primary for the zone
  -> The zone contains a delegation of to,
  ( NS
  -> BUT the 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
Question by:arhc
    LVL 25

    Accepted Solution

    Have you checked the items mentioned in the error?  Specifically, I'd start with the forwarders and root hints: make sure, if you're using forwarders, that they're only pointing to legitimate DNS servers outside of your network (unless you're using conditional forwarders in a multi-domain environment), and make sure that your root hints list is fully populated.  There's a button to copy the list from another server (one of your ISP's servers, for example) if it isn't.

    Both of these can be checked by right-clicking your server's name in the DNS console and selecting Properties.

    Author Comment

    Thanks sage i got the solution....

    DNS servers were forwarding to themselves i remove them from nameservers now working fine.

    Featured Post

    Better Security Awareness With Threat Intelligence

    See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

    Join & Write a Comment

    This article is intended as an extension of a blog on Aging and Scavenging by the MS Enterprise Networking Team. In brief, Scavenging is used as follows: Each record in a zone which has been dynamically registered with an MS DNS Server will have…
    I've written instructions for one router type, but this principle may be useful for others of the same brand and even other brands of router. Problem: I had an issue especially with mobile devices that refused to use DNS information supplied via…
    Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…
    Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

    729 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    21 Experts available now in Live!

    Get 1:1 Help Now