dns resolving itself

  • Thread starter Thread starter jose
  • Start date Start date
J

jose

this is driving me crazy!

1) Forwarders is disabled
2) Master lists of secondary zones does not contain itself.
3) Notify lists of primary zones - not sure how to check this in w2k, the
articles I find on this is for nt4.
4) Delegations of subzones. Must not contain NS record for this DNS
server unless subzone is also on this server - can someone clarify this?

thanks a lot!
jose


---------------------------

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 7/28/2004
Time: 4:30:20 PM
User: N/A
Computer: PUMBAA
Description:
The DNS server encountered a packet addressed to itself -- IP address
x.x.x.x.

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 server admin should
remove the offending NS record.
Data:
0000: 50 25 00 00 P%..
 
jose said:
this is driving me crazy!

1) Forwarders is disabled
2) Master lists of secondary zones does not contain itself.
3) Notify lists of primary zones - not sure how to check this in w2k, the
articles I find on this is for nt4.
4) Delegations of subzones. Must not contain NS record for this DNS
server unless subzone is also on this server - can someone clarify this?

thanks a lot!
jose


---------------------------

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 7/28/2004
Time: 4:30:20 PM
User: N/A
Computer: PUMBAA
Description:
The DNS server encountered a packet addressed to itself -- IP address
x.x.x.x.

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 server admin should
remove the offending NS record.
Data:
0000: 50 25 00 00 P%..
Click to expand...


Is this machine dual homed?
If not, usually you can configure a forwarder to get rid of this. See if it
helps.

To clarify #4:
4) Delegations of subzones. Must not contain NS record for this DNS
server unless subzone is also on this server - can someone clarify this?
Click to expand...

It means that if you are delegating a child zone to another DNS, then that
other DNS needs to be in the NS records for the delegation, not your server,
unless you are delegating the subzone to yourself, such as what the _msdcs
zone does in Windows 2003.

--
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 - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Back
Top