Windows Server / DNS, DHCP & Server Networking
Review scavenging before investigating disappearing DNS records
Dynamic records can disappear because of aging configuration, failed refresh or another authorized change. Check policy before disabling cleanup.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-DnsServerScavenging -ComputerName DNS01Read the result
The server-level settings are only part of scavenging behavior; zone aging and individual record timestamps also matter.
Resolve and verify
Compare the deletion time with zone settings and client refresh activity. Repair the failed registration or incorrect aging design and monitor the record through a normal refresh cycle.
Before changing production
Do not globally disable scavenging or make all dynamic records static without assessing stale-record accumulation.