Windows Server / DNS, DHCP & Server Networking
Investigate external-name failures on a Windows DNS server
Internal names can resolve while external queries fail because forwarding, recursion or upstream connectivity differs.
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-DnsServerForwarder -ComputerName DNS01Read the result
The command reports configured forwarders and associated settings for the selected server. It does not prove those upstream resolvers currently answer.
Resolve and verify
Test an approved external name through the server, compare forwarder reachability and inspect DNS events. Repair the intended upstream path and validate internal names as well.
Before changing production
Do not replace enterprise forwarding with an arbitrary public resolver or expose recursive DNS to the internet.