Aging & Scavenging of W2K DNS Records

[Richard Phillips]

Does anyone have any recommendations/Best Practices regarding the Aging &
Scavenging of W2K DNS records??

A note from the "Managing the Aging Scavenging of Server Data" TechNet
document

CLIP>>>>>>>>>>>>>>>

 REFRESH INTERVAL - This period is based on the frequency in which DHCP
clients renew their IP address leases with the server. Typically, this
occurs when 50% of the scope lease time has elapsed. If the Windows 2000
default scope lease duration of 8 days is used, then the maximum refresh
period for records updated by DHCP servers on behalf of clients is 4 days.

ENDCLIP>>>>>>>>>>>>>>>

So my main question to the group is: has anyone seen a best practice, or
better
than default recommendation regarding the "Aging & Scavenging of DNS records
in W2K DNS?

My thought is:  If you have long lease times defined for clients, then you
should put it for at least 88% of the longest lease time.  This will give
put you at the T2 (Actually 87.5%, but who's counting) renewal time in the
event that a lease hasn't been properly renewed the first time (due to
Server or Network issues).  For example if the lease time is 21 days, then
the default scavenging will remove the updated record before its 50% lease
(T1) time has arrived, then it will get deleted.  So for this configuration,
you should have a "refresh interval" value of at lease 18.375 (which is
87.5% of a 21 day lease), or really 19.

What does anyone else think???

Rich Phillips