Archived from groups: microsoft.public.win2000.dns (More info?)
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.
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.
Facebook
Twitter
Instagram