Dns timestamp not updating

6854933580_2c8b688306_z

Some problems associated with stale records are: unnecessary space utilization long zone transfers, wrong resolution of the client query due to stale data, and accumulation of stale records on the DNS server can degrade its performance.These stale records problems can be resolved by the aging and scavenging features.Refresh interval This is the time period in which the resource records can be refreshed.Resource record refresh: This is a DNS dynamic update without changing the hostname and IP address.Tick the box “Scavenge Stale resource Records” and leave the rest to their defaults. The No-Refresh and Refresh Intervals are not when resource records get scavenged.

Assuming your Active Directory is already set up, with the requisite domain, zone, and name servers configured, there are a few items within DHCP and DNS you’ll want to configure.

When the client dynamically updates its DNS information in this situation, the client's DNS time stamp is not updated until the Refresh interval takes effect.

This behavior controls and manages DNS and Active Directory replication (for AD Integrated Zones).

The first thing we need to do is enable Scavenging. To enable scavenging on all zones see “Enable Scavenging on All Zones” below.

To enable scavenging right click the DNS zone, select properties and then on the general tab select the “ageing” button.

For some environments, especially smaller ones where network changes are somewhat infrequent, this may not be a big deal.

You must have an account to comment. Please register or login here!