DNS Scavenging

Guys

if I want to just mark with timestamp all the records for a zone, without let the server to remove stale resource records. what I want to do is mark all the records with timestamp, wait around 3 weeks (21 days) and then when all the records are marked, enable scavenging.

Which would be the correct proceddure (REAL WORLD) to achieve this?

Thanks very much.
M7KAsked:
Who is Participating?
 
ChiefITConnect With a Mentor Commented:
There's no need to mark a record with a time stamp. Clients do this as they register within DNS.

There are two intervals within DNS scavaging. There is a no-refresh and a refresh interval. By default, they are set to 7 and 7. This means that the DNS record will scavage (or be deleted) on the 15th day.

You want DNS scavaging to be a day or two longer than your DHCP lease duration. Then, a client with a new lease will not get the DNS record delted before getting a lease update.

Just enable scavaging. That's really all you have to do, if your DHCP lease duration is the default duration of (I believe 9 days).
0
 
M7KAuthor Commented:
Hi MinoDC

Thanks for that but unfortunately it does not answer my question.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Leon FesterSenior Solutions ArchitectCommented:
dnscmd /ageallrecords

Usage: DnsCmd <ServerName> /AgeAllRecords <ZoneName> [<NodeName>] [/Tree] [/f]
    <Zone>     -- <ZoneName>
    <ZoneName> -- FQDN of a zone
    <NodeName> -- name or node or subtree in which to enable aging
                   - "@" for zone root OR
                   - FQDN of a node (name with a '.' at the end) OR
                   - single label for name relative to zone root
    /Tree      -- force aging on entire subtree of node
                    or entire zone if node not given
    /f         -- execute without asking for confirmation
Command failed:  ERROR_INVALID_PARAMETER     87    0x57

Just be aware that even static and CNAME records will be aged.
0
 
M7KAuthor Commented:
Chief

Thanks for that, but as far as I understand, if I enable scavenging without aging all the records, records that are older than the timestamp when enable scavenging (today) will be removed, even static. so we need to age all the records first.
0
 
MinoDCCommented:
0
 
Leon FesterSenior Solutions ArchitectCommented:
You've seem to have missed my post....read the one above ChiefIT.
0
 
Leon FesterSenior Solutions ArchitectCommented:
Ignore my previous post...I've re-read what you've just posted.
Sorry ChiefIT...earlier post wasn't aimed at you.

I don't think you understand what aging records do.
Aging a record will set the time stamp on a DNS entry, so that when scavenging is enabled it deletes all records older than the current date.

You cannot set the age of a DNS record to be newer than today. i.e. you cannot set the age of a record to be 05/15/2011 if today is 05/12/2011.

Aging a record, gives the time stamp of the current day/time.

If you want to set your records NOT to be deleted when scavenging then set a high Lease time on your DHCP server, and recreate your static entries.

Any manually created record A or CNAME will not have the timestamp set so it will not be removed by scavenging.

You can use the DNSCMD command to do bulk insert of any static entries, A or CNAME that you may need.
0
 
Justin OwensITIL Problem ManagerCommented:
Enabling DNS Scavenging should not remove static DNS entries, only dynamic ones.  If you are worried about that, though, just export your DNS records.  If scavenging removes them, then you can import them again.

DrUltima
0
 
ChiefITConnect With a Mentor Commented:
As long as you take into consideration the DHCP lease duration and do not scavage records before the DHCP lease duration ends, the dynamic entries will NOT be erased. Static entries will not be erased either.

Let's look at that another way. Static entries will not be erased, as Dr. Ultima stated. So, that leaves dynamic updates. These will not be deleted either because the DHCP address was renewed and the client registered during that time. So, these records will be TOO NEW to scavage.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.