Windows Server - DNS "Delete this record when it becomes stale"

Asked By Jerem on 18-Jul-08 01:26 PM
I have 4 DCs in 2 sites.  1 forward lookup zone,  My DCs
and my mail servers keep getting the "Delete this record when it becomes
stale" box checked.  I uncheck it, and look at it later and it is checked
again.  I have tried deleting and recreating the record, when I create the
record the box in unchecked, later it is checked again.

How do I make it so that these records are not aged?

Replication is to all DNS servers in the Active Directory Forrest.
Dynamic updates is set to Non-secure and Secure.


Blake replied on 18-Jul-08 04:24 PM
check one of those DCs network config (TCP/IP properties) - is it set to
'register this connection in DNS?'
Jerem replied on 19-Jul-08 01:30 AM
I think the trick is to disable the DHCP client service.
Kevin D. Goodknecht Sr. [MVP] replied on 19-Jul-08 12:23 PM
Read inline please.

Do not disable the DHCP Client service, it is required for DNS
registrations. Why would you want the DCs to not be able to keep their DNS
records up to date?
Unless you have set the scavenging time to way to short of a time, there
would be no reason to worry about the checkbox.

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.
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
Keep a back up of your OE settings and folders
with OEBackup:
Ace Fekay [MVP] replied on 20-Jul-08 03:27 AM
Jeremy <Jeremy@> typed:

You're seeing default behavior when it comes to static (manually created)
entries or machines with with static IPs registering. What record(s) are you
deleting and re-creating? DCs will auto register their host and SRV records.
That is the basis of how and why AD works. If you attempt to alter this
behavior, there are certain rules concerning what needs to be registered in

Can you elaborate on this? Also, the DHCP client service does two things:
DNS registration, and name resolution, whether the machine has a static IP
or DHCP config, despite it's name. That's a crucial service an something you
really don't want to disable, as Kevin mentioned, on any machine, especially
a DC.

Jerem replied on 24-Jul-08 12:29 PM
I have several Servers that as soon as I turn on scavenging their A record
disappears.  I have tried unchecking the "Delete this record when it becomes
stale" but that box keeps getting rechecked and the records are being

My DHCP server is out of my control and there is NOTHING that I can do with
it.  the DHCP lease time is 4 hours.  Scavenging is set to No-Refresh 2 hours
and the Refresh is set to 2 hours.

The scavenging period is set to 8 hours.

I need to have scavenging working, but I cant have server A records
disappearing every day.  Suggestions ?
Ace Fekay [MVP] replied on 27-Jul-08 06:45 PM
Jeremy <Jeremy@> typed:

Minimum scavenging time, if I remember, is one day. However this conflicts
with the DHCP lease of 4 hours. This will cause issues. Read this article
(scroll past the ads to get to the answer):