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

DNS Config Issue

I seem to be having a couple issues with my DNS server. i am posting the error... PLEASE HELP!


Event Type:      Warning
Event Source:      DNS
Event Category:      None
Event ID:      7062
Date:            2/15/2009
Time:            2:00:51 PM
User:            N/A
Computer:      ITTLMC1
Description:
The DNS server encountered a packet addressed to itself on IP address 10.18.18.3. The packet is for the DNS name "196.15.18.10.in-addr.arpa.". 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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 50 25 00 00               P%..    
0
epipkin
Asked:
epipkin
1 Solution
 
WeirdoBcCommented:
Does your DNS server have a 15.18.10.in-addr.arpa Reverse Lookup zone? Does the server who have that zone (if any) is in the forwarder list?
0
 
jalilthe1Commented:
Event ID 7062
Source DNS
Type Error

Description: DNS Server encountered a packet addresses to itself -- IP address <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 server 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
Example: -> This DNS server dns1.microsoft.com is the primary for the zone microsoft.com. -> You have delegated the zone bar.microsoft.com to bardns.bar.microsoft.com and are NOT running the bar.microsoft.com zone on this DNS (dns1.microsoft.com). Note, you should make this check (with nslookup of 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.

Good Luck
Jalilthe1
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

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