If you immediately (with respect to using the ageall switch) tell the scavenging server to scavenge all records, wouldn't you expect all the records to be scavenged at that point? Wouldn't it be better to mark them all, and wait a cycle or two of refresh prior to pushing the issue?
Otherwise, the most immediate way to do this would be to delete the zone. I don't recommend that however :) On 12/7/06, Daniel Gilbert <[EMAIL PROTECTED]> wrote:
I have a rather off the wall DNS scavenging question. I have a bunch of DNS records that are stale and need to be scavenged out of the zone. Following the O'REILLY book: DNS on Windows Server 2003 I have configured aging and scavenging. (Don't ask why this wasn't done when the zone was first setup, that is another story) Now I know: If scavenging is disabled on a standard zone and you enable scavenging, the server does not scavenge records that existed before you enabled scavenging. The server does not scavenge those records even if you convert the zone to an Active Directory–integrated zone first. To enable scavenging of such records, use the AgeAllRecords in Dnscmd.exe. I know this must be done in order to configure existing records to a scavengable state. Is there a way to immediately force a scavenge cycle that will remove all stale records? I would not to have to wait unitl the "no-refresh" and "refresh" intervals expire. Daniel Gilbert List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir@mail.activedir.org/
