Dns timestamp not updating
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.Recall that computer accounts are also security principals and therefore deleting the object and recreating the object results in a NEW object with a different SID.In other scenarios, when a change is made on the DHCP server such as configuring the DHCP service to update DNS records on behalf of the client, the DHCP server may not update a DNS record when the client registers a DNS record.In the case of using the DHCP service to register client's DNS records, you need to add the DHCP server's computer account to the DNSUpdate Proxy Security group and set the appropriate settings on the DHCP server's properties.In this case, the DNS client registers the host (A) resource record.Before using aging and scavenging features of DNS some conditions needed are: 1) Aging and scavenging features must be enabled on the DNS server and on the zone. 2) Resource records must be added dynamically to the zone or manually modified to be used in operations of aging and scavenging.Aging Aging is the process of identifying stale DNS records.
If the computer account in the domain is DELETED and then recreated for the same computer, the DNS record is not updated with the new SID for the computer account.
Aging and Scavenging is a DNS server service which supports a mechanism for performing clean-up and removal of stale resource records which can accumulate in zone data over time.
It helps to maintain the dynamic DNS environment by regular deletion of stale resource records from the DNS database.
It is important to understand how clients update their DNS records dynamically to prevent issues where the process fails due to poor management of your DNS zones and records.
Many DNS administrators find that the Dynamic DNS update process, and aging/scavenging processes may be difficult to understand and manage correctly.