DNS Server Not Responding: Diagnosing Name Resolution Failures

The message “The DNS server isn’t responding” or “Your computer appears to be correctly configured, but the device or resource is not responding” is produced by Windows Network Diagnostics when a DNS query sent to the configured resolver received no reply before the timeout. The machine has an IP address and a default gateway; what it lacks is an answer to the question “what address belongs to this name?” The failure is in name resolution, not in the link layer, and the distinction matters because the repair is different.

A DNS server that does not respond is not the same as a name that does not exist. When a resolver replies with NXDOMAIN, the query reached a server and the server answered that the name has no record. That is a working DNS path with a negative answer. When the resolver does not respond, the query left the machine and nothing came back. The first case points at the name or the zone; the second points at the path to the resolver, the resolver itself, or something intercepting the traffic.

What the diagnostic is actually reporting

Network Diagnostics sends a query to the DNS server configured on the active adapter and waits. If no response arrives, it reports the server as not responding. The configured server is usually the router’s address, because the router handed itself out as the DNS server over DHCP. The router then forwards queries to the ISP’s resolver. A failure anywhere along that chain - the router’s DNS relay, the ISP resolver, or a local interceptor - produces the same message on the client.

Confirm the scope before changing anything

Separate name resolution from routing with two tests. First, ping a literal IP address that should be reachable, such as the default gateway or a well-known public address. A reply to the IP proves the adapter, the link, and the route to that address are working. Second, ping a name. If the IP responds and the name does not, the fault is in DNS. If neither responds, the problem is routing or the link, and the DNS message is a symptom of a machine that cannot reach anything.

ping 1.1.1.1

A reply here means the network path to that address is intact. Request timed out means the machine cannot reach even a numeric address, and DNS is not the first thing to repair.

ping www.example.com

A reply with a resolved address means DNS is working for that name. “Ping request could not find host” means the name did not resolve, which is the condition the diagnostic reported.

Query the configured server and a public resolver

nslookup can be pointed at a specific server, which isolates whether the configured resolver is the failing component.

nslookup www.example.com

With no server argument, nslookup uses the resolver configured on the adapter. A timeout here, after the IP test succeeded, indicates the configured resolver is not answering.

nslookup www.example.com 1.1.1.1

This sends the same query directly to a public resolver. If this returns an answer while the default query times out, the configured resolver - usually the router - is the failing element, and the path to the internet is fine. If both time out, the problem is broader than one resolver: routing, a firewall, or a VPN intercepting port 53.

ipconfig /all

Read the “DNS Servers” line for the active adapter. If it lists an address that is not the current gateway and not a resolver the network is known to use, the adapter is pointed at a server that no longer exists on this network. That happens after moving a laptop between networks, after a VPN client leaves a stale setting, or after a router is replaced and the old address is retained.

Flush the resolver cache

The local DNS cache can hold a negative or stale entry that outlives the condition that created it. Flushing it is non-destructive and costs nothing.

ipconfig /flushdns

“Successfully flushed the DNS Resolver Cache” confirms the cache was cleared. Re-run the nslookup test afterward; if the name now resolves, the fault was a cached entry.

ipconfig /displaydns

This lists the current cache contents before a flush.

Change the DNS server as a diagnostic and a fix

The adapter’s DNS setting is changed in the network adapter properties. Open Settings, Network & Internet, then the adapter’s properties, and edit the DNS server assignment. The same dialog is reached through Control Panel, Network and Sharing Center, Change adapter settings, then the adapter’s Properties, Internet Protocol Version 4, Properties. Set the preferred server to a public resolver and the alternate to a second one. This is a diagnostic: if names resolve after the change, the previous resolver was the fault. It is also a fix when the previous resolver is one the user does not control.

netsh interface ip set dns name="Ethernet" static 1.1.1.1

This sets the preferred DNS server on the named interface. The interface name must match the one shown by ipconfig; “Ethernet” and “Wi-Fi” are common but not universal.

netsh interface ip set dns name="Ethernet" dhcp

This returns the adapter to obtaining DNS from DHCP, which restores the router as the resolver. Use it after the diagnostic to undo the manual setting if the original resolver is preferred.

Restart the router’s DNS relay

When the configured resolver is the router and the public resolver answers, the router’s DNS forwarding process has stopped responding. A power cycle of the router clears it. This is the most common cause of the message on a home network, and it is also the case the user can fix without changing any setting on the computer.

When the carrier or ISP owns the equipment

If the router is supplied by the ISP and locked, the DNS relay cannot be restarted independently of the device. If the ISP resolver itself is down, no setting on the computer restores it; the public resolver test will succeed while the ISP resolver fails. In both cases the repair belongs to the provider. Changing the adapter to a public resolver works around an ISP resolver outage, but it does not repair the provider’s equipment, and the setting must be reverted if the network requires the ISP resolver for internal names.

What people get wrong about this

The natural response to “DNS server not responding” is to change the DNS server, because the message names the DNS server. That is a reasonable reading of the text and it is wrong often enough to matter. The configured server is usually the router, and the router is usually forwarding to the ISP. Changing the adapter to a public resolver makes the symptom disappear while leaving the failing component in place, which means the next device on the network, or the next DHCP lease, meets the same failure. The test that separates the cases is the direct query to a public resolver: if that succeeds, the path is fine and the configured resolver is the fault; if it fails, the resolver was never the problem.

A second misreading treats the message as a general internet outage. The IP ping settles it. A machine that can reach a numeric address has a working network and a broken name service; a machine that cannot reach a numeric address has a routing or link problem, and repairing DNS will not restore it. The diagnostic reports what it was asked to test, which is name resolution, not overall connectivity.

A third mistake is to apply a manual DNS setting and forget it. A laptop configured with a public resolver on a corporate network may fail to resolve internal names that only the corporate resolver knows. The setting is a diagnostic first and a fix second, and it should be reverted when the original resolver is restored.