Windows Server 2022 – DNS scavenging removes critical static records unexpectedly – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Critical hostnames disappear from DNS, causing intermittent service resolution failures and failed application dependencies.

Environment & Reproduction

Occurs when scavenging is enabled globally and aging is accidentally enabled on static-record zones.

Get-DnsServerScavenging
Get-DnsServerZoneAging -Name 

Root Cause Analysis

Static records received stale timestamps or zone aging intervals are too aggressive for update cadence.

Quick Triage

Confirm missing records, zone aging status, and most recent scavenging run.

Get-DnsServerResourceRecord -ZoneName  -Name 
Get-EventLog -LogName DNS Server -Newest 100

Step-by-Step Diagnosis

Review record timestamps and compare no-refresh/refresh windows to actual client update cycles.

Get-DnsServerResourceRecord -ZoneName  | Select HostName,Timestamp,RecordType
Get-DnsServerZoneAging -Name 

Solution – Primary Fix

Disable aging for static-sensitive zones and recreate critical records with protected settings.

Set-DnsServerZoneAging -Name  -Aging $false
Add-DnsServerResourceRecordA -ZoneName  -Name  -IPv4Address 

Solution – Alternative Approaches

Keep aging enabled but tune intervals and reserve static records in dedicated non-aging subzone.

Set-DnsServerZoneAging -Name  -Aging $true -NoRefreshInterval 7.00:00:00 -RefreshInterval 7.00:00:00

Verification & Acceptance Criteria

No further unintended deletions across two scavenging cycles; monitoring confirms stable name resolution.

Resolve-DnsName 
Get-DnsServerScavenging

Rollback Plan

Restore previous zone aging policy and import DNS records from backup export if required.

Import-DnsServerZone -Name  -FileName 

Prevention & Hardening

Separate dynamic and static records by zone design and require change approval for scavenging policy edits.

Related Errors & Cross-Refs

Often accompanied by DHCP update conflicts and stale PTR record accumulation.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn: DNS aging/scavenging best practices and enterprise zone hygiene for AD-integrated DNS.