Windows Server / DNS, DHCP & Server Networking
Check a conditional forwarder for a partner domain
Only one namespace may fail because its conditional forwarder targets stale addresses or uses the wrong replication scope.
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-DnsServerZone -ComputerName DNS01 -Name 'partner.example.com'Read the result
The zone's type and properties help identify whether the namespace is managed as a forwarder. Inspect its configured master servers using the supported DNS tools.
Resolve and verify
Compare the intended partner resolvers and network path with the failing namespace. Correct the specific forwarding configuration through its owner and retest representative names.
Before changing production
Do not add a local primary zone for the partner domain to hide failed forwarding.