Re: obsolete DNS entries in AD-integrated DNS
- From: "Paul Bergson [MVP-DS]" <pbergson@xxxxxxxxxxxxxxxxx>
- Date: Tue, 6 Mar 2007 08:08:13 -0600
There are actually two places you need to enable scavenging. The one as
listed by Keshav and on the server that is to do the scavenging. It is
recommended to only have 1 dns server scavenge for each dns zone to be
scavenged.
See my other post that will link you to a how to for scavenging.
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"Keshav" <Keshav@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7FEDCCBE-68B8-4424-A0EB-FC3E1ECB88F8@xxxxxxxxxxxxxxxx
You could probably use the Scavanging/Aging options of the DNS server to
delete DNS records that have not been updated in a defined period of time.
Open DNS Management console > Right-Click the DNS server > Properties. You
have the options there under "Advanced"
"dcdc" wrote:
In an AD-integrated DNS server, there are a lot of obsolete DNS entries
due
to a same client gets multiple DHCP IP addresses and multiple clients
gets a
same IP address (re-use).
How to set the DNS server to drop those obsolete entries?
Thanks,
.
- Follow-Ups:
- References:
- obsolete DNS entries in AD-integrated DNS
- From: dcdc
- obsolete DNS entries in AD-integrated DNS
- Prev by Date: Re: DHCP Server authorized but will not lease IP
- Next by Date: Re: schema changes
- Previous by thread: obsolete DNS entries in AD-integrated DNS
- Next by thread: Re: obsolete DNS entries in AD-integrated DNS
- Index(es):
Relevant Pages
|
Loading