Event ID - 7062

  • Thread starter Thread starter Edgar
  • Start date Start date
E

Edgar

What is this?
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 7/12/2004
Time: 11:30:47 AM
User: N/A
Computer: Hornet
Description:
The DNS server encountered a packet addressed to itself
on IP address 192.168.8.10. The packet is for the DNS
name "139.163.81.63.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%..


How do i resolve this? Everything is working fine with
no problems. I am just very precaucious when it comes to
warnings.
 
In
Edgar said:
What is this?
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 7/12/2004
Time: 11:30:47 AM
User: N/A
Computer: Hornet
Description:
The DNS server encountered a packet addressed to itself
on IP address 192.168.8.10. The packet is for the DNS
name "139.163.81.63.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%..


How do i resolve this? Everything is working fine with
no problems. I am just very precaucious when it comes to
warnings.
Click to expand...

Setup a forwarder to your ISP's DNS and see if this goes away (should take
care of it).

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
In
Edgar said:
What is this?
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 7/12/2004
Time: 11:30:47 AM
User: N/A
Computer: Hornet
Description:
The DNS server encountered a packet addressed to itself
on IP address 192.168.8.10. The packet is for the DNS
name "139.163.81.63.in-addr.arpa.". The packet will be
discarded. This condition usually indicates a
configuration error.
Click to expand...

That reverse lookup IP is delegated to another DNS server, I assume yours.
What is your DNS server using for a forwarder?
Does it have itself listed in the root hints?

Do you have any delegations on this DNS server, with itself listed as the NS
for the delegation?
 
the dns forwarders are set to our isp's dns server. as
for the root hints, it does not have itself listed. root
hints (fqdn) start at a and stop at m.root.servers.net

I'm checking with our isp if there dns servers have
changed. btw, is this error message something to worry
about.
 
In
edgar said:
the dns forwarders are set to our isp's dns server. as
for the root hints, it does not have itself listed. root
hints (fqdn) start at a and stop at m.root.servers.net

I'm checking with our isp if there dns servers have
changed. btw, is this error message something to worry
about.
Click to expand...

Its a configuration issue.
http://www.eventid.net/display.asp?eventid=7062&source=

If you have more than one DNS, individually forward to the ISP. If the ISP
does not support forwarding to (which will show up with another error) then
choose another forwarder. You can use 4.2.2.2 to test it (it works fine).

Since you have 3 child domains (or one Root and two child domains?), we;ll
need to know how your DNS infrastructure is setup. This may be the cause of
it all.

So:
Did you delegate from the parent to the child and then forward from the
child to the parent and from the parent forward to the ISP (this is the
proper way to do it). If not, depending on how you did it, may be causing
the issue.

Please describe your configuration.


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
In
edgar said:
the dns forwarders are set to our isp's dns server. as
for the root hints, it does not have itself listed. root
hints (fqdn) start at a and stop at m.root.servers.net

I'm checking with our isp if there dns servers have
changed. btw, is this error message something to worry
about.
Click to expand...

What about my third question?
 
Back
Top