• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 491
  • Last Modified:

DNS problem

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
Computer:          
Description:
The DNS server encountered a packet addressed to itself on IP address 10.10.2.5. The packet is for the DNS name "l2.zedo.com.edgesuite.net.". 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
0
arhc
Asked:
arhc
1 Solution
 
DrDave242Commented:
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.
0
 
arhcAuthor Commented:
Thanks sage i got the solution....

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

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now