G
Guest
I'm running a DNS server with an AD-integrated zone, configured with secure
dynamic updates (on Windows Server 2003 DC). When browsing
the records in the zone, I see that there are records whose machines are
valid and still active but when you look at their time stamp, the date is a
few months old. We plan to enable scavenging (with the default parameters)
and are very concerned that once the scavenging starts, it sees these
records as
old and will start removing those valid records with old time stamp.
Could anyone address this concern? These valid records were NOT manually
added or modified. Theory says that these records should re-register (hence
updates the time stamp) every 24 hours, among other conditions. For some
reason, it does not appear to do so. Did I miss something?
Thanks for any reply on this ...
smo
dynamic updates (on Windows Server 2003 DC). When browsing
the records in the zone, I see that there are records whose machines are
valid and still active but when you look at their time stamp, the date is a
few months old. We plan to enable scavenging (with the default parameters)
and are very concerned that once the scavenging starts, it sees these
records as
old and will start removing those valid records with old time stamp.
Could anyone address this concern? These valid records were NOT manually
added or modified. Theory says that these records should re-register (hence
updates the time stamp) every 24 hours, among other conditions. For some
reason, it does not appear to do so. Did I miss something?
Thanks for any reply on this ...
smo