scavenging not working - still!

I am revisiting this issue, as it still exists

I have a reverse zone (among other things) with nearly 4000 records, most of
which are 3+ years old. This zone is set to scavenge, the server is set to
scavenge, and the records are not set to 'do not scavenge'. Yet the records
persist, months after initially turning the scavenging on.

?????

Is there a log for this function? Or some way I can trouble shoot it?

Thanks
Blake

 

Read inline please.

In

Before zones can be scavenged, scavenging has to be enabled on the server,
as well as the zone.
To enable scavenging on the server, select the server properties sheet in
the DNS Management console, Advanced tab, select "Enable automatic
scavenging of stale records" then set the scavenging period to 1 day longer
than your DHCP lease period.
To enabled scavenging on the zone, bring up the zone properties sheet, on
the General tab, click the Aging button and select "Scavenge stale resource
records"
Scavenging will log in the event log, see:
http://support.microsoft.com/kb/842006/en-us




--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

 

I appreciate your comments Kevin, however:

1) I've already enabled scavenging on both the zone and the server (some
months ago, actually)
2) I get an event when scavenging is triggered, but it doesn't remove the
offending records

Right now it appears the DHCP leases are set to 8 days, and I have
scavenging setup for the default (7 days). I will make this correction and
report back.

Blake

 

In

Static addresses will not purge since they have an infinite TTL.

Ace

 

My problem is I have, for example, 15 records for 192.168.0.1 (15 "1's" in
the reverse zone). I want the scavenger to delete all the "1's" with an old
stamp and leave the new ones (no static addresses)

This zone is old and scavenging was never turned on before. I have a
reverse zone for a Class C which as nearly 4 THOUSAND records.

It isn't pretty.

 

In

Is there anything in the DNS Event logs? If not, try increasing logging in
DNS properties and see what shows up in the Event logs.

Also, are they all static entries or were they all DHCP entries?

Ace

 

They should all be DHCP entries

 

In

Sorry if this was addresses (trying to remember back) but did you add the
DHCP server to the DnsProxyUpdate group? If so, unfortunately it will not
delete previously created entries. Look at one of the previous entries not
being scavenged. What is it's TTL? (Put it in Adv view to see that info).

Also, there is a time delay with scavenging as well.

Ace

 

Adding the account to that group removes the benefit of secure updates (or
so the MS docs I have read on the subject say).

The account which is running DHCP should have read/write to all the records
(I have set it up as an AD user, which is a member of a group which as full
access). I DID change the user that DHCP was using to register the records,
however. (It was using a computer account and that machine was replaced, so
I set it up as a domain user). I have to think that is part of the issue,
as I've never seen this before.

Also - if the scavenging is a function of the DNS server, why would the DHCP
permissions matter? (not arguing, just curious)

The TTL for some I checked is 15 minutes.

Blake

 

In

Not necessarily part of scavenging, but if DHCP owns the record, it will
update a record with its new IP instead of creating a new one with the old
one still there.

As for as the way you did it, I haven't tried that and not able to comment
on it. Sorry.

Ace