Messy Reverse Look-up Zones

[Rich Magowan]

W2K, Multiple DNS servers AD integrated. I defined reverse
lookup zones for all my network segments. Basically I use
a 10. addressing scheme inside. I created one reverse
lookup zone for 10.in-addr.arpa and let DNS create the sub-
domain records for all the networks in the 10. range that
I use. The problem is the pointer records, I get multiple
pointer records for the same host with different names
associated with each pointer record. This is, of course,
due in part to DHCP and the workstations releasing and
renewing IP addresses. Why doesn't DNS just overwrite the
esisting pointer record with the new name information? Did
I miss something in setting up the reverse look-up zones?
Should I have setup each zone seperately? Is there any
mechanism avaliable to "clean-up" my reverse look-up zones
such that there is only one pointer record per machine?
Any guidance is greatly appreciated.
Thanks.

 

[Ace Fekay [MVP]]

W2K, Multiple DNS servers AD integrated. I defined reverse
lookup zones for all my network segments. Basically I use
a 10. addressing scheme inside. I created one reverse
lookup zone for 10.in-addr.arpa and let DNS create the sub-
domain records for all the networks in the 10. range that
I use. The problem is the pointer records, I get multiple
pointer records for the same host with different names
associated with each pointer record. This is, of course,
due in part to DHCP and the workstations releasing and
renewing IP addresses. Why doesn't DNS just overwrite the
esisting pointer record with the new name information? Did
I miss something in setting up the reverse look-up zones?
Should I have setup each zone seperately? Is there any
mechanism avaliable to "clean-up" my reverse look-up zones
such that there is only one pointer record per machine?
Any guidance is greatly appreciated.
Thanks.

Hi Rich,

You'll want to enable Scavenging. That should clean it up.

Enable automatic scavenging of stale resource records:
http://www.microsoft.com/windows2000/en/server/help/sag_DNS_pro_EnableAutoma
ticScavenging.htm

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

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

 

[Herb Martin]

Keep your Scavening periods and Refresh settings LONGER
than you think they should be.

One week for each of the three settings (the default) is a VERY
GOOD choice.