We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

DNS recursive query error

steverpayne
steverpayne asked
on
Medium Priority
753 Views
Last Modified: 2012-08-13
We seem to be having some problems with the DNS server. The error is in the recursive query and wanted to know how to fix it. May be it has something to do with the other server we have our secondary server?
Log Name:      DNS Server
Source:        Microsoft-Windows-DNS-Server-Service
Date:          2/8/2009 12:25:45 PM
Event ID:      7062
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Schwarz18.dmsas.local
Description:
The DNS server encountered a packet addressed to itself on IP address 129.250.35.250. The packet is for the DNS name "apps.bzresults.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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DNS-Server-Service" Guid="{71A551F5-C893-4849-886B-B5EC8502641E}" EventSourceName="DNS" />
    <EventID Qualifiers="32768">7062</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-02-08T17:25:45.000Z" />
    <EventRecordID>169612</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>DNS Server</Channel>
    <Computer>Schwarz18.dmsas.local</Computer>
    <Security />
  </System>
  <EventData Name="DNS_EVENT_SELF_SEND">
    <Data Name="param1">129.250.35.250</Data>
    <Data Name="param2">apps.bzresults.net.</Data>
    <Binary>50250000</Binary>
  </EventData>
</Event>

Open in new window

Comment
Watch Question

Chris DentPowerShell Developer
CERTIFIED EXPERT
Top Expert 2010

Commented:

Hey,

The error message is quite explicit about what you should check. Have you done any of that? Or are you not sure of how to do that?

Chris

Author

Commented:
not sure how to do that. Not fimilar with 2008 really so I don't want to change anything.

Author

Commented:
In the forward lookup zone  (msdcs.dmsas.local) the Name Server is using the server with the error and also the secondary. Should I remove Schwarz18 from this?
Chris DentPowerShell Developer
CERTIFIED EXPERT
Top Expert 2010

Commented:

Only if the server doesn't hold a copy of _msdcs. I take it that folder is greyed out in the dmsas.local zone? If so, check the NS Records it shows when you select it.

Chris
Figured out the problem,  someone made changed to the NIC DNS servers and therefore giving the error messages. I also found out that we were using the wrong DNS servers for our external DNS. problem Fixed.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.