Because of the time it takes scavenging to do it’s thing people find this command and get tempted to give it a try. Before a server will even look at a record to see if it will be scavenged the zone must have scavenging enabled.
A change to a record means a change that must be replicated.
After the (Record Timestamp) (No-refresh interval) elapses we enter the Refresh interval.
The refresh interval is the time when refreshes to the timestamp are allowed. The client is allowed to come in and update it’s timestamp.
DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.
Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy. There are two big issues with DNS scavenging that seem to come up a lot: This post should help us figure out when the first issue will happen and completely avoid the second.