Windows Server / DNS, DHCP & Server Networking
Compare an authoritative Windows DNS record with the client answer
A client can cache an older answer while the authoritative zone is already correct. Inspect the managed zone directly before editing it.
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-DnsServerResourceRecord -ComputerName DNS01 -ZoneName 'corp.example.com' -Name 'app01'Read the result
With DNS Server tools, this reads the selected record from the specified server. It is not the same path as a client recursive lookup.
Resolve and verify
Compare record data and TTL with the affected client's approved resolver answer. Correct the authoritative record only when it is actually wrong, then verify cache aging and service reachability.
Before changing production
Do not delete all records for a name without checking aliases and application dependencies.