About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Staff can reach the file server and sign in to the domain, but public websites fail to load, Microsoft 365 is slow to connect, or nslookup for an outside name returns Server failed or times out. The internal zones are fine. The fault is in how the Windows DNS server answers names it does not host.
For a name outside its own zones, a Windows DNS server works through a fixed order: its own zones and cache, a matching conditional forwarder, a delegation, the server-level forwarders, and finally the root hints, all within one overall time limit (Microsoft Learn, DNS forwarding in Windows Server). The checks below find the step where resolution stops.
What you see
nslookup www.microsoft.comfrom a workstation returns Server failed, Query refused, or Request to server timed out, whilenslookupfor an internal server name works.- External names resolve slowly, or work for a while and then stop until the DNS Server service restarts.
- One namespace (a partner domain, a second internal forest) fails while the internet works.
- Workstations or servers that bypass the internal DNS (pointed straight at a public resolver) resolve outside names but have trouble joining or signing in to the domain.
Why it happens
Forwarders that do not answer. Server-level forwarders handle anything the local zones, conditional forwarders and delegations do not cover. Microsoft notes that the server does not judge whether an unresponsive forwarder is offline or just slow, so forwarder health has to be monitored separately.
The overall timeout runs out first. RecursionTimeout is the time budget for the whole query. Per-forwarder timeouts schedule attempts inside that budget and do not extend it. If several forwarders fail to answer before the budget is spent, the server returns SERVFAIL without reaching the root hints. Microsoft says configuring many forwarders does not guarantee every forwarder is tried.
Forwarder ordering on Windows Server 2022 and later. By default the server reorders forwarders by response time and resets to the configured order about every 15 minutes. Microsoft notes that in Windows Server 2022 and later, if none of the forwarders respond, the server uses only the first server in the dynamic list for later queries until the DNS Server service restarts.
Root hint fallback switched off or unusable. After the forwarders are exhausted, the server falls back to the root hints only if recursion is allowed, UseRootHint is true, the budget has time left, and the server can reach the root servers. With no forwarders configured, the root hints are the only starting point.
Recursion disabled. If recursion is turned off on the server, it normally returns REFUSED for anything that needs recursion.
A root zone on the server. Microsoft's DNS client guidance says that to forward or use root hints for internet names, any root "." zone in Forward Lookup Zones must be deleted (Microsoft Learn, DNS client settings). A server that hosts the root of a private namespace acts as a root server for it.
Conditional forwarders with no way out. If a conditional forwarder's targets do not answer and its Use recursion setting is off, the query fails. A conditional forwarder cannot be created for a name the server already hosts as a zone; the hosted zone keeps answering.
Clients pointed at the wrong servers. Microsoft's guidance is that domain controllers and domain members should not list an internet provider's DNS servers in their own network settings. The internal DNS server forwards to them instead.
How to prove the cause
1. Query the DNS server directly from a workstation, using its IP address (Microsoft Learn, Troubleshooting DNS servers):
nslookup <internal name> <IP address of the DNS server>
nslookup <external name> <IP address of the DNS server>
Internal works and external fails: the problem is recursion. Microsoft reads the responses this way: Server failure or Query refused can mean a paused zone or an overloaded server; Request to server timed out or No response from server suggests the DNS Server service is not running or is not listening on that address.
2. Clear the server cache and repeat, so an old failure is not answered from cache:
Clear-DnsServerCache
(dnscmd /clearcache does the same. Microsoft notes Clear-DnsClientCache clears the server's own client cache, which is a different thing.)
3. Check the event logs on the DNS server: Application, System and DNS Server.
4. Check the forwarders. In the DNS console, open the server's properties, Forwarders tab. If forwarders are listed, test each one the same way as step 1, from the DNS server, with the forwarder's IP address in place of the DNS server's. A forwarder that times out from the DNS server is a cause to fix.
5. If there are no forwarders, test the root servers. From the DNS server:
nslookup
server <IP address of server being examined>
set q=NS
.
The final . line, which asks for the root servers, is added here to Microsoft's example. A list of root servers means the server can reach the root; a failure further down points to a broken delegation for the name in question. A timeout means checking Root Hints in the server properties and whether the server can reach the root servers at all, or whether a firewall is in the way.
6. Look for a root "." zone under Forward Lookup Zones.
7. For one failing namespace, look in Conditional Forwarders for a matching zone, its targets, and its Use recursion setting.
8. Check the clients' own DNS settings with ipconfig /all on a domain controller and a workstation. They should list internal DNS servers only.
The fix
Replace or remove forwarders that do not answer. Use forwarders you trust and can reach. Microsoft recommends multiple healthy forwarders when redundancy is needed, with forwarding and recursion timeouts that give enough time to reach them.
On Windows Server 2022 and later, if the server sticks to one dead forwarder until restart, Microsoft documents turning off dynamic reordering so it cycles through all forwarders as earlier versions did:
Set-DnsServerForwarder -EnableReordering $falseDecide on root hint fallback. Keep it (
Set-DnsServerForwarder -UseRootHint $true) if the server may resolve directly when forwarders fail. Turn it off only if policy says every outside query must go through the forwarders, and back that with firewall rules.Check the timeout budget when three or more forwarders are configured. The overall limit is set with
Set-DnsServerRecursion -Timeoutand the per-forwarder wait withSet-DnsServerForwarder -Timeout. Microsoft advises checking the effective behaviour with monitoring and packet captures rather than assuming.Re-enable recursion if it was switched off on a server that internal clients use for internet names. Microsoft advises allowing recursion only for trusted clients and networks, never for untrusted ones.
Delete a stray root "." zone if the server should resolve internet names. Destructive step: first confirm the server is meant to resolve internet names and is not deliberately the root of a private namespace. Check the zone type in DNS Manager. An Active Directory-integrated zone is stored in AD DS and replicates to the other DNS servers that hold it (Microsoft Learn, DNS zone types), so deleting it there removes it from all of them. Keep a copy first. For a file-backed zone, copy the zone file. For an Active Directory-integrated zone, use
Export-DnsServerZone -Name "." -FileName root-zone-backup.dns, which Microsoft describes as a troubleshooting export, not a file-backed zone file (Microsoft Learn, Export-DnsServerZone).Fix conditional forwarders: correct the targets, and turn on Use recursion only if another path is valid for that namespace. If the namespace is hosted locally as a zone, migrate and remove that zone before creating the forwarder, or use a delegation for a child namespace.
Point clients at internal DNS servers only, and have those servers forward to the provider. After changing a server's own DNS client settings, Microsoft says to run
ipconfig /flushdnsandipconfig /registerdns.
How to confirm the fix
nslookup <external name> <IP address of the DNS server>returns an address, after clearing the server cache.- The same lookup works from a workstation using its normal settings, and internal names still resolve.
- With one forwarder deliberately unreachable (in a planned test), lookups still succeed through the next forwarder or the root hints, as designed.
What to watch afterwards
- Forwarder response and failures. Microsoft states the forwarding behaviour is not a substitute for health monitoring.
- Internet provider or firewall changes that change which outside resolvers the server may reach.
- Recursion and root hint settings after server builds or hardening changes.
- New domain controllers and servers with an internet provider's DNS servers in their network settings.
Read next
Related articles you may want next.
- TroubleshootingClean Up Stale AD DNS Records: Scavenging Without Deleting Live OnesStale DNS records in an AD-integrated zone? Understand no-refresh and refresh intervals and timestamps, list records by age first, then enable scavenging on one server safely.Read article
- TroubleshootingPort Forward Works From the Internet but Not Inside: NAT Hairpin or Split DNSPublic name works outside but not on the LAN? Prove the NAT hairpin fault with captures, then choose hairpin NAT (DNAT plus SNAT) or split DNS with the TLS name intact.Read article
- TroubleshootingDNS event 4013 after a restart: why a domain controller takes 15 minutes or more to startA domain controller sits at Preparing network connections for up to 25 minutes and logs DNS event 4013. Find out why DNS and Active Directory are waiting on each other, prove it, then stagger restarts and set the DNS client order so a working DNS server is always reachable.Read article
Risks and limits
- Turning recursion on for networks you do not trust exposes an open resolver. Limit it to internal clients.
- Changing timeouts or forwarders affects every lookup the server makes for outside names; change one setting at a time and test.
NXDOMAINandNODATAare valid final answers and do not trigger a fallback. A forwarder that wrongly says a name does not exist will not be bypassed.- This covers the Windows DNS server resolving outside names for internal clients. Public DNS hosting for your own domain is a separate topic.
Sources
- Microsoft Learn, "DNS forwarding in Windows Server", applies to Windows Server 2016–2025, last updated 30 September 2026: https://learn.microsoft.com/en-us/windows-server/networking/dns/forwarding
- Microsoft Learn, "Troubleshooting DNS servers", applies to Windows Server 2016–2025, last updated 20 June 2025: https://learn.microsoft.com/en-us/windows-server/networking/dns/troubleshoot/troubleshoot-dns-server
- Microsoft Learn, "Best practices for DNS client settings in Windows Server" (KB 825036), last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/best-practices-for-dns-client-settings
- Microsoft Learn, "DNS zone types" (Active Directory-integrated zone replication): https://learn.microsoft.com/en-us/windows-server/networking/dns/zone-types
- Microsoft Learn, "Export-DnsServerZone": https://learn.microsoft.com/en-us/powershell/module/dnsserver/export-dnsserverzone
Next step
When internal names work and the internet does not, the answer is in which resolution step the DNS server reaches and where it stops. NetLeverage has looked after business servers since 2002. If your office DNS is failing on outside names, talk to us through managed support with the nslookup results and the server's forwarder list.
This article was originally published on .