DNS Warning in event viewer

Posted on 2006-06-22
Medium Priority
Last Modified: 2010-07-27
I am continuously getting this warning in the event viewer. i have an active directory integrated DNS server (ip

The DNS server encountered a packet addressed to itself -- 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 this DNS server unless subzone is also on this server.
Example of self-delegation:
  -> This DNS server dns1.foo.com is the primary for the zone foo.com.
  -> The foo.com zone contains a delegation of bar.foo.com to dns1.foo.com,
  (bar.foo.com NS dns1.foo.com)
  -> BUT the bar.foo.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

I have not enabled Forwarders list

other things pls let me know  where to look at.

Thanks in advance

Question by:venkataramanaiahsr
  • 6
  • 2
  • 2

Expert Comment

ID: 16967428
Check the "root hints" section too and make sure the server's own IP isn't listed there.

Author Comment

ID: 16967822
there is no entry of this ip in root hints.

Expert Comment

ID: 16967880
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

LVL 20

Expert Comment

ID: 16969149
check through your zones and see if any of them could not be loaded. I've seen this problem when a server was set to use root hints, changed to forwarders, and then back to root hints.

The reverse lookup zone got corrupted in that case.

Author Comment

ID: 16973991
i see some similarity in the actions i did on active directory integrated dns server and  the comment posted by "brwwiggins".  Intially the domain controller was built without connecting to the internet. hence there were two entries in dns console .  one is . and another is domain name. hence the forwarders were not enabled.  because of  this i could not connect to the internet ( which is thro winxp internet sharing from different machine) from the client machine  if i give  the ip address of domain controller
(active directory integrated dns)  in  primary dns place  though i give ip address of win xp machine  in default gateway.
I had to give  ip address of winxp m/c in both default gateway and primay dns inorder to access internet from cliet machine.

 To aviod this i deleted  . entry to enable forwarders  and once i gave dns address of my isp in forwarders list.
  then i removed it from the forwarders list.

  now my internet problem is solved.  whichever machine i need to enable internet all i have to do is give winxp
system's ip address in default gateway. now the primary dns server ip address of all the clients is ip address of my active directory integrated dns server.  

now when i go to dns console only forward look up zone contains  A record of all hosts connected to this domain controller. there is record in reverse look up zone.

now is this the problem and if so how to rectify it. i think this also explains the  reason  for my above problem and solution about internet sharing.

so, Dear "brwwiggins" pls explain the complete technical flow how this happened immeditaely

Thanks in advance

LVL 20

Accepted Solution

brwwiggins earned 2000 total points
ID: 16987075
do you have the DNS server pointing to itself for DNS resolution? Do not include the ISP as a secondary DNS to your server under the network properties of the server. It should only have itself and another AD-integrated DNS server for your domain if one exists.

When we ran into this problem, the DNS server was trying to register itself in DNS as all clients do. However, instead of registering the IP address and hostname on it's own DNS services it was trying to register with the hosts that were set as forwarders earlier. These hosts were configured to point dns requests for my domain back to the AD-integrated server....basically a loop. The registration request was going out to another server, which refers back to my DNS server, and then my DNS server throws up an error because it received a request to register itself.

The only way I could resolve the issue was to delete the zones and re-create them in AD.

Author Comment

ID: 16991761
i have only one entry in my ad integrated dns server setting i,e ip address  pointing to itself.  there are no other entries. I have only one domain controller in my network and one additonal domain controller both in the same ip range and subnet mask . the host which were set as forwarders ( now there are no entries in forwarders) are the dns servers of my isp and i dont think the dns servers of my isp are configured to my domain which is configured with internal ip.

pls explain.

also pls tell me how to go about deleting  the zones  and recreating in AD


Author Comment

ID: 17017555
when i ran netdiag /fix i got the following result

DNS test ...................................Passed
[WARNING] Cannot find a primary authoritative DNS server for the name
 'daserver.srinivasa.com.'. [RCODE_SERVER_FAILURE]
 The name 'daserver.srinivasa.com.' may not be registered in DNS.

   PASS - All the DNS entries for DC are registered on DNS server '
 and other DCs also have some of the names registered.

is this the problem and how to rectify it

pls reply immediately as i am getting this msg every few seconds


Author Comment

ID: 17017560
this msg means dns  warning 7062 in event viewer

Author Comment

ID: 17017752
another thing.  now there is another entry in my dns console called cached lookups

  daserver (computername0
    Cached Lookups

tilldate it was not there  now when i open dns console  this new entry was there .  all i rememebr  is i  stopped and started netlogon service , ran netdiag /fix couple of times

i just want know whether it is normal or my dns is  corrupted.

pls explain immediately

Featured Post

Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
In this article, we will see two different methods to recover deleted data. The first option will be using the transaction log to identify the operation and restore it in a specified section of the transaction log. The second option is simpler and c…
Planning to migrate your EDB file(s) to a new or an existing Outlook PST file? This video will guide you how to convert EDB file(s) to PST. Besides this, it also describes, how one can easily search any item(s) from multiple folders or mailboxes…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.
Suggested Courses

601 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