DNS aging on the reverse lookup zone

[Sam]

We have aging enabled on both our forward and lookup zones (and on the
DNS server itself), but for some reason the reverse lookup entries are
being scavenged.

I have used dnscmd to age all records, and when i open the DNS file,
most entries do have an age entry, but they just aren't being deleted.
We have some PCs that were removed months ago that still have around
20 reverse lookup entries.

Does anyone have any idea why scavenging isn't taking place? Even any
logs or other places I can check?

As a side issue, does anyone know how to read the timestamp value?
Once such entry is 3527664 but I have no idea what that translates to.

 

[Herb Martin]

We have aging enabled on both our forward and lookup zones (and on the
DNS server itself), but for some reason the reverse lookup entries are
being scavenged.

Well, that's because you have it on.

Maybe you mean "not being scavenged"?

I have used dnscmd to age all records, and when i open the DNS file,
most entries do have an age entry, but they just aren't being deleted.
We have some PCs that were removed months ago that still have around
20 reverse lookup entries.

Does anyone have any idea why scavenging isn't taking place? Even any
logs or other places I can check?

1) It isn't (really) on for the domain or more likely Zone

2) The RefreshInterval, NoRefreshInterval, PLUS the Scavening Period
is longer than you are expecting

3) the Records were entered manually

4) Something is re-registering the records (even though you think those
machines
are gone) -- maybe the DHCP, on behalf of NEW clients using same address

5) a bug?