Tutorials

How to diagnose and fix DNS server errors in Windows 10 and 11

By Noura Mint Ely · November 16, 2026

Advertisement
Ad disclaimer: For links on this page, DESKING APP may earn a commission from the provider. This supports our work and has no influence on our editorial rating.
How to diagnose and fix DNS server errors in Windows 10 and 11
Advertisement
Table of contents
  1. How to Fix DNS Server Errors in Windows
  2. Understand the error
  3. Identify the scope
  4. Run basic tests
  5. Clear the DNS cache
  6. Change DNS servers
  7. Renew network settings
  8. Restart DNS services
  9. Check browser DNS
  10. Inspect firewall rules
  11. Check the Hosts file
  12. Reset TCP/IP and Winsock
  13. Update network drivers
  14. Diagnose company DNS
  15. Check multiple resolvers
  16. Investigate one domain
  17. Verify the repair
  18. Frequently Asked Questions

How to Fix DNS Server Errors in Windows

A “DNS server not responding” error means Windows cannot complete a domain name lookup with the DNS resolver configured on the computer.

The cause may be a failed router DNS service, an unavailable provider resolver, incorrect adapter settings, a firewall rule, a damaged local cache, or a problem with the DNS server itself.

You can identify the failing point with Windows tools such as ipconfig, nslookup, Resolve-DnsName, and Event Viewer.

The correct repair depends on the test results.

If every device on the network fails, investigate the router or internet provider first.

If only one Windows computer has the problem, inspect its DNS settings, VPN, firewall, and network adapter.

This tutorial follows that order, from simple checks to advanced diagnostics, and covers Windows 10 and Windows 11.

Understand the error

DNS, or Domain Name System, translates domain names into IP addresses.

When you enter a website address in a browser, Windows asks a DNS resolver for the corresponding address before the browser can connect to the web server.

If the resolver does not answer, returns an error, or cannot be reached, the browser may display “DNS server not responding,” “DNS_PROBE_FINISHED_BAD_CONFIG,” or another name resolution error.

The message does not identify the failed component.

A computer can have a working Ethernet or Wi-Fi connection and still fail DNS queries.

It may also access a website by IP address while failing to open the same destination by domain name.

That difference is useful because it separates basic network connectivity from name resolution.

Common causes include:

  • Unavailable DNS server: The resolver supplied by the router, internet provider, or company network does not respond.
  • Incorrect DNS configuration: The adapter points to an old, mistyped, or unreachable DNS address.
  • Router problems: The router's DNS proxy or forwarding service has stopped responding.
  • Cached records: Windows has retained an outdated or invalid DNS response.
  • Firewall restrictions: Windows Firewall, endpoint security, or a network firewall blocks DNS traffic.
  • VPN or proxy interference: A VPN changes DNS settings or routes queries through an unavailable server.
  • Network adapter problems: A driver or TCP/IP configuration issue prevents normal communication.
  • DNS server faults: A company DNS server may have stopped, lost its forwarders, or failed to load a required zone.

The first diagnostic decision is whether the problem affects one computer, one network, or a particular domain.

Do not change several settings at once.

Record each test result so you can identify which change actually restores name resolution.

Identify the scope

Before changing Windows settings, test another device on the same network.

Connect a phone or another computer to the same router and open several unrelated websites.

If those devices also fail, the problem is unlikely to be limited to the Windows DNS cache or adapter.

Use this comparison to decide where to investigate:

Test resultMost likely areaNext action
All devices fail on the same networkRouter, provider, or shared DNSCheck router and WAN status
One Windows computer failsWindows configuration or softwareInspect adapter and DNS settings
Only one browser failsBrowser configuration or secure DNSTest another browser and browser DNS
Only one website failsDomain, authoritative DNS, or cached recordTest the domain with another resolver
Internal company names fail, public websites workCorporate DNS or VPNCheck internal DNS and VPN settings
Public names fail, internal company names workForwarder or external DNS pathTest the configured resolver and upstream access


The distinction between a device failure and a shared network failure prevents unnecessary repairs.

For example, changing DNS on one computer will not fix a router that has lost its upstream connection.

Likewise, restarting the router may interrupt every user in an office when the fault is actually a single workstation.

Check whether the problem affects both wired and wireless connections.

If the same computer fails on Ethernet and Wi-Fi, its Windows configuration or security software deserves attention.

If Ethernet works but Wi-Fi fails, investigate the wireless network path.

If another computer works through the same cable and port, the original device is the more likely source of the fault.

Run basic tests

Windows includes several commands that help separate DNS failures from general connectivity problems.

Open Command Prompt from the Start menu, or right click Start and select Terminal.

You can use Command Prompt or PowerShell for the commands below.

Start with the basic IP configuration, then test the gateway and a public IP address before testing domain names.

Follow this sequence:

  1. Inspect the adapter: Run ipconfig /all. Locate the active Ethernet or Wi-Fi adapter and record its IPv4 address, default gateway, DHCP status, and DNS Servers. Ignore disconnected adapters, VPN interfaces, and virtual adapters unless they are part of the connection under investigation.
  2. Test the local gateway: Use ping followed by the Default Gateway address shown by ipconfig. A reply confirms that the computer can communicate with that local address, although some routers block ping and may not respond.
  3. Test an external IP address: Run ping 1.1.1.1. If the address responds but websites do not load by name, DNS becomes a stronger suspect. A failed ping is not definitive because some networks block ICMP traffic.
  4. Test a domain name: Run nslookup example.com. The output identifies the DNS server Windows used and whether it returned an address or timed out.
  5. Compare another resolver: Run nslookup example.com 1.1.1.1. This sends the query directly to Cloudflare's public resolver instead of relying on the DNS server configured for the adapter.

A successful response from the public resolver, combined with a timeout from the configured resolver, points toward the configured DNS server or the path to it.

If both queries time out, the problem may involve routing, firewall rules, provider restrictions, or the wider internet connection.

If both succeed but a browser still fails, inspect the browser's own DNS settings, proxy, cache, and security extensions.

The results also help interpret common messages.

A timeout means no usable response arrived within the query period.

NXDOMAIN means the resolver says the requested domain name does not exist.

SERVFAIL means the resolver could not complete the query.

These responses indicate different conditions and should not all be treated as proof that the DNS server is offline.

Advertisement

Clear the DNS cache

Windows stores DNS responses temporarily to avoid repeating lookups for names it has recently resolved.

This local resolver cache can contain a negative response as well as a successful address.

VPN

NordVPN

4.8
4.8

This NordVPN Review for 2026 covers its server network, no logs policy, security features, pricing tiers, and what you get for your money.

  • Massive server network globally
  • RAM only servers for privacy
  • Prices jump after first year
  • Fewer features in basic plan

If a domain's DNS records have changed, or Windows has cached an incorrect response, clearing the cache can force a fresh query.

BleepingComputer documents the Windows flush procedure, which uses the built in ipconfig command.

Run it after recording the current DNS configuration, especially if the problem affects only one domain or began after a DNS change.

  1. Open an elevated terminal: Right click Start and select Terminal (Admin) or Windows PowerShell (Admin). Approve the User Account Control prompt.
  2. Flush the cache: Enter ipconfig /flushdns and press Enter. Windows should report that the DNS Resolver Cache was successfully flushed.
  3. Inspect the cache if needed: Run ipconfig /displaydns to view cached records. This is useful when investigating a specific domain that continues to return an unexpected result.
  4. Repeat the lookup: Run nslookup example.com, replacing the example domain with the name that failed. Then open the same domain in a browser.
  5. Compare the result: If the domain now resolves, the local cache may have contained an outdated or negative response. If the query still fails, continue to the DNS server tests.

The flush command clears the Windows DNS client cache.

It does not clear the cache held by a router, company DNS server, browser, or internet provider.

If the same incorrect result appears on multiple devices, the stale record may exist upstream.

A local cache flush cannot correct a DNS record that is wrong at the authoritative DNS provider.

Do not confuse ipconfig /flushdns with a reset of the network stack.

The former clears cached name resolution data; it does not remove the configured DNS server, renew the IP address, or rebuild the network adapter.

Use the narrower repair first because it changes less of the system.

Change DNS servers

If the configured resolver is unavailable but another resolver answers correctly, you can test a different DNS provider.

Common public resolvers include Cloudflare and Google Public DNS.

Cloudflare's standard IPv4 addresses are 1.1.1.1 and 1.0.0.1.

Google's IPv4 addresses are 8.8.8.8 and 8.8.4.4.

These services are alternatives for general internet name resolution.

They are not automatically suitable for every office, school, VPN, or managed network.

A company may depend on internal DNS to locate domain controllers, file servers, printers, business applications, and private hostnames.

Replacing those DNS addresses with public resolvers can break internal services even if public websites begin to load.

For a personal computer on a home network, use the following procedure to test Cloudflare DNS on Windows 11:

  1. Open network settings: Select Start, open Settings, then choose Network & internet.
  2. Select the active connection: Choose Wi-Fi if the computer uses wireless, or Ethernet if it uses a cable. Open the properties for the connected network.
  3. Find DNS assignment: Locate DNS server assignment and select Edit. Windows normally shows Automatic (DHCP) when the router or DHCP server supplies DNS addresses.
  4. Choose manual configuration: Select Manual from the drop down list and enable IPv4. Enter 1.1.1.1 as the preferred DNS address and 1.0.0.1 as the alternate address.
  5. Save the configuration: Select Save and close Settings. If IPv6 is active and you intend to configure it as well, use the corresponding IPv6 resolver addresses rather than entering IPv4 addresses in the IPv6 fields.
  6. Test the new resolver: Open Command Prompt and run nslookup example.com. Confirm that the response identifies the configured public resolver and returns an address.
  7. Test real applications: Open multiple websites and the applications that originally failed. A successful command line lookup is useful, but the repair is not complete until the affected services work.

For Windows 10, open Settings, select Network & Internet, then Status and Change adapter options.

Right click the active Ethernet or Wi-Fi connection, select Properties, and open Internet Protocol Version 4 (TCP/IPv4).

Select Use the following DNS server addresses, enter the preferred and alternate addresses, and select OK.

Cloudflare's Windows setup documentation describes this procedure and the corresponding IPv6 values.

The following table compares common public resolver addresses.

Choose one provider for the initial test rather than mixing unrelated services without a reason.

ProviderPreferred IPv4Alternate IPv4Typical use
Cloudflare1.1.1.11.0.0.1General public DNS resolution
Google Public DNS8.8.8.88.8.4.4General public DNS resolution
Cloudflare Families malware filter1.1.1.21.0.0.2DNS filtering for malware domains


Cloudflare also provides a family resolver that blocks selected categories of domains.

Filtering behavior is different from ordinary DNS resolution, so do not select a filtered resolver if you need unrestricted name resolution for a particular test.

A filtered response can be mistaken for a DNS failure when the resolver is deliberately blocking the requested domain.

After testing, restore the original setting if the public resolver does not improve the connection.

In Windows 11, return to DNS server assignment, select Edit, and choose Automatic (DHCP).

In Windows 10, reopen the IPv4 properties and select Obtain DNS server address automatically.

This restores DNS assignment from the network's DHCP service.

Advertisement

Renew network settings

A DNS failure can originate from an incorrect IP configuration rather than the resolver itself.

Windows may have an expired DHCP lease, an incorrect gateway, or a DNS address that no longer belongs to the current network.

Renewing the DHCP configuration asks the network's DHCP server for updated settings, including the address, gateway, and DNS information when those options are supplied by DHCP.

Use this procedure if ipconfig /all shows an unexpected address, an incorrect gateway, or DNS servers that should no longer be in use.

It is particularly relevant after moving a laptop between networks or changing a router.

  1. Open an administrator terminal: Right click Start and select Terminal (Admin). Use Command Prompt if Terminal opens in PowerShell and you prefer the traditional interface.
  2. Release the current lease: Run ipconfig /release. Windows releases the DHCP configuration on the active adapters that use automatic addressing, temporarily disconnecting those interfaces.
  3. Request a new lease: Run ipconfig /renew. Wait for the command to finish and check whether Windows receives an IP address and gateway.
  4. Review the new settings: Run ipconfig /all again. Confirm that the active adapter has the expected address, gateway, and DNS server list.
  5. Clear cached records: Run ipconfig /flushdns, then repeat the nslookup test for the domain that failed.

If ipconfig /renew reports that the DHCP server cannot be contacted, investigate the local network and DHCP service.

A computer with a 169.254 address has usually assigned itself an automatic private address because it did not receive a usable DHCP lease.

This can result from a disconnected router, a disabled DHCP service, a switch port on the wrong VLAN, or a DHCP relay failure on a managed network.

Do not use release and renew on a computer with a manually configured static IP address unless you understand the consequences.

The commands are intended for adapters that obtain their configuration automatically.

On a server, printer, point of sale terminal, or office workstation with a fixed address, record the existing settings and confirm the network policy before making changes.

Restart DNS services

Windows includes a DNS Client service that supports name resolution and maintains the local DNS cache.

If the service is stopped or malfunctioning, Windows applications may experience name resolution problems.

The service is normally managed by Windows, so do not change its startup type or attempt to disable it as a routine repair.

Check the service status through PowerShell:

  1. Open Start, search for PowerShell, and select Run as administrator.
  2. Enter Get-Service Dnscache and press Enter.
  3. Review the Status column. The service should normally show Running.
  4. If it is not running, inspect the service error and Windows event logs before attempting a repair.
  5. Restart the computer if the service is stuck or cannot be restarted through normal Windows controls.

On some Windows installations, the DNS Client service is protected and cannot be restarted through the Services console or a simple PowerShell command.

That behavior is not necessarily an error.

Avoid changing service permissions, registry settings, or dependencies to force a restart.

Restarting Windows is the safer first option for clearing a temporary service state.

The DNS Client service on a Windows workstation is different from the DNS Server service on Windows Server.

A workstation normally acts as a DNS client and sends queries to a resolver.

A Windows Server configured with the DNS Server role can answer queries for other computers and may also forward external queries.

Restarting the server role without understanding its effect can interrupt name resolution for an entire network.

Check browser DNS

A browser can use its own secure DNS configuration instead of the resolver assigned to Windows.

Chrome, Edge, and Firefox support DNS over HTTPS, which sends DNS queries inside HTTPS connections.

This can create a difference between the result of nslookup in Command Prompt and the result seen in a browser.

If nslookup resolves a domain correctly but one browser still reports a DNS error, check the browser's secure DNS setting.

A browser may be configured to use a provider that is blocked, unavailable, or incompatible with the current network.

A company firewall may also apply different rules to browser HTTPS traffic and conventional DNS requests.

For Google Chrome or Microsoft Edge, follow these steps:

  1. Open the browser settings and search for Secure DNS.
  2. Locate the security or privacy section that contains the Secure DNS setting.
  3. Check whether the browser uses the current service provider or a manually selected provider.
  4. If a custom provider is configured, temporarily switch to the current service provider or disable the custom selection for a controlled test.
  5. Restart the browser and open the affected domain again.
  6. Restore the preferred secure DNS policy after the test, especially if the device is managed by an organization.

Firefox has its own DNS over HTTPS controls under Settings, Privacy & Security, and DNS over HTTPS.

The exact options can vary by version and region.

If the browser uses a custom resolver, compare its behavior with Windows DNS using nslookup.

A successful lookup in Windows combined with a failure in only one browser points toward browser configuration, browser extensions, or its secure DNS provider.

Do not disable encrypted DNS permanently just to remove an error message.

DNS over HTTPS can protect DNS queries from being read or modified by parties on the network path.

The goal is to identify whether the browser's resolver is the failing component and then configure an approved resolver that works with the network's security policy.

Advertisement

Inspect firewall rules

DNS queries normally use UDP port 53, and TCP port 53 is also required for certain DNS operations and responses.

A firewall that blocks these connections can cause timeouts even when general internet access is available.

Microsoft documents DNS client failures caused by outbound firewall rules that block UDP port 53, as well as cases where third party security software interferes with DNS traffic.

Start with the least disruptive checks:

  • Windows Firewall: Review outbound rules that apply to DNS traffic. Do not disable the entire firewall to test a single service.
  • Endpoint security: Check whether antivirus, web protection, endpoint detection, or traffic filtering software has a DNS protection feature.
  • VPN firewall: Inspect VPN policy if DNS stops working only after the VPN connects.
  • Router firewall: Check whether DNS traffic is restricted between the client network and the configured resolver.
  • Corporate firewall: Ask the network administrator whether UDP and TCP port 53 are permitted to the approved DNS servers.

For a more detailed check, open Windows Defender Firewall with Advanced Security.

Search for Windows Defender Firewall with Advanced Security from Start, then inspect Outbound Rules.

Look for custom rules that block DNS, the DNS Client, or the relevant security application.

A standard workstation normally does not require a manually created outbound block for DNS.

PowerShell can test whether a TCP connection to a DNS server's port 53 succeeds.

VPN

NordVPN

4.8
4.8

This NordVPN Review for 2026 covers its server network, no logs policy, security features, pricing tiers, and what you get for your money.

  • Massive server network globally
  • RAM only servers for privacy
  • Prices jump after first year
  • Fewer features in basic plan

Replace the example address with the actual resolver address:

Test-NetConnection 1.1.1.1 -Port 53

Review the TcpTestSucceeded field in the output.

A True result confirms that a TCP connection to that address and port was established.

A False result does not prove that all DNS traffic is blocked, because ordinary DNS queries commonly use UDP and some public resolvers may treat TCP tests differently.

Use nslookup as the primary DNS query test, and treat the TCP test as additional evidence.

If you manage the firewall, verify that the policy allows DNS traffic from the client subnet to the intended resolver.

Avoid opening DNS access indiscriminately from the internet to internal DNS servers.

Publicly exposed recursive DNS services can be abused, and a company resolver should normally accept queries only from approved networks.

Check the Hosts file

Windows checks its local Hosts file before sending a query to a DNS server for a name.

An incorrect entry can therefore send a domain to an old or unintended IP address even when the DNS resolver is working properly.

This is especially relevant if the problem affects one domain consistently, while nslookup returns a correct address.

The Hosts file is stored at:

C:\Windows\System32\drivers\etc\hosts

To inspect it safely:

  1. Open Notepad as administrator. Search for Notepad in Start, right click it, and select Run as administrator.
  2. In Notepad, select File, then Open.
  3. Browse to C:\Windows\System32\drivers\etc.
  4. Change the file type selector from Text Documents to All Files so the Hosts file becomes visible.
  5. Open hosts and inspect entries that contain the domain name that fails.
  6. If an entry is clearly incorrect and you are authorised to change it, remove or comment out that specific line, then save the file.

A Hosts entry maps a name to an IP address.

For example, a line that maps a public website to an old private address can prevent the browser from reaching the correct server.

Lines beginning with the number sign are comments and are not used for name resolution.

Do not delete the entire file or remove entries you do not understand, because administrators and development tools may use deliberate mappings.

Microsoft's DNS client troubleshooting documentation describes the Hosts file as part of the Windows name resolution sequence.

If you use a company computer, check with IT before editing it.

Some organizations intentionally use local entries for testing, internal services, or security controls.

Reset TCP/IP and Winsock

If DNS queries continue to fail after checking the resolver, adapter settings, and firewall, Windows network components may have a damaged or inconsistent configuration.

The TCP/IP stack handles network communication, while Winsock provides the interface used by applications to access network services.

Resetting these components can correct certain configuration problems, but it may also affect custom network software and settings.

Use this repair only after the earlier tests.

Open Terminal or Command Prompt as administrator, then run the following commands in order:

  1. Reset Winsock: Run netsh winsock reset. Windows should confirm that the Winsock Catalog was reset and indicate that a restart is required.
  2. Reset TCP/IP: Run netsh int ip reset. Review the output for errors and note any entries that could not be reset.
  3. Clear the DNS cache: Run ipconfig /flushdns to remove cached resolver entries.
  4. Renew DHCP settings: If the adapter uses automatic addressing, run ipconfig /release and then ipconfig /renew.
  5. Restart Windows: Reboot the computer so the network stack can load with the reset configuration.
  6. Repeat the diagnostic tests: Run ipconfig /all and nslookup example.com. Confirm that the correct DNS servers appear and that queries receive responses.

A network reset is not a substitute for correcting a firewall rule or an unavailable DNS server.

If the same DNS resolver remains unreachable after the reset, investigate the path between the computer and that server.

If the problem started immediately after installing a VPN, security product, or virtual network application, inspect that software before repeating the reset.

Windows 11 provides a graphical Network reset option under Settings, Network & internet, Advanced network settings, and Network reset.

Windows 10 provides it under Settings, Network & Internet, Status, and Network reset.

This option removes and reinstalls network adapters and restores their settings to defaults.

It can require VPN software to be reinstalled and static IP or custom DNS settings to be restored, so record those details before proceeding.

Advertisement

Update network drivers

A damaged or incompatible network adapter driver can interfere with communication between Windows and the network interface.

This can affect DNS queries even when the adapter appears connected.

Driver troubleshooting is more relevant when the problem began after a Windows update, driver installation, hardware change, or repeated network failures on one computer.

Use Device Manager to inspect the adapter:

  1. Right click Start and select Device Manager.
  2. Expand Network adapters and identify the active Ethernet or Wi-Fi device.
  3. Right click the adapter and select Properties.
  4. Open the General tab and review the Device status message for errors.
  5. Open the Driver tab and record the driver provider, date, and version.
  6. If the problem began after a driver update, select Roll Back Driver if Windows makes that option available.
  7. If no rollback is available, obtain the correct driver from the computer or adapter manufacturer's official support page.

Avoid third party driver update utilities that install packages without confirming the exact hardware model.

A driver intended for a similar adapter may not support the same hardware revision.

If the computer has no internet access, download the driver on another device and transfer it with a USB drive.

After installing or rolling back the driver, restart Windows and repeat the DNS tests.

If the same adapter fails on several networks, the driver or hardware deserves further investigation.

If it works on another network but fails on one office or home network, check that network's DNS and access policies instead.

Diagnose company DNS

Business networks often use internal DNS servers rather than public resolvers.

A Windows computer joined to an Active Directory domain may depend on DNS records that identify domain controllers, Kerberos services, LDAP, file servers, and internal applications.

Replacing the assigned DNS addresses with Cloudflare or Google can break these services, even if public websites start to load.

If the computer is connected to a company network, first identify the DNS addresses assigned to the active adapter.

Run ipconfig /all and note the DNS Servers, Connection-specific DNS Suffix, IPv4 address, and Default Gateway.

Compare the results with a working computer on the same VLAN or office network.

Differences can reveal an incorrect DHCP scope, wrong static configuration, or a client connected to the wrong network segment.

Use nslookup to query the internal DNS server directly.

Replace the example address and hostname with values supplied by the network administrator:

nslookup servername.company.local 192.168.10.10

A successful answer confirms that the specified server returned a record for that name.

If the internal query fails but a public domain resolves, investigate the internal DNS service, zone, network path, or VPN connection.

If the internal name resolves but public names fail, inspect the DNS server's forwarders or its ability to perform external recursion.

For an administrator managing Windows Server DNS, the server side investigation should include:

  • Service status: Confirm that the DNS Server service is running.
  • Server interfaces: Verify that the DNS service listens on the IP address used by clients.
  • Forwarders: Check that configured forwarders are correct and reachable.
  • Zones: Confirm that required forward and reverse lookup zones are loaded and active.
  • Firewall: Verify that approved clients can reach the server on DNS ports.
  • Event logs: Review the DNS Server, System, and Application logs for service or query errors.

Microsoft's DNS server troubleshooting guidance recommends checking the server's IP configuration and using nslookup to query a specific DNS server.

A timeout may indicate that the service is stopped, the server is not listening on the requested interface, or a firewall is blocking the query.

A response such as SERVFAIL or Query refused points toward a different server side condition and needs examination of the zone, recursion, or server policy.

DNS normally uses UDP port 53 for queries and can use TCP port 53 for larger responses and other operations.

A firewall that permits one protocol but blocks the other can cause some DNS operations to fail.

Administrators should verify both protocols where the network design requires them, rather than assuming that a successful ping proves DNS is available.

Advertisement

Check multiple resolvers

Windows can have more than one DNS server configured on an adapter.

The secondary address provides another resolver when the preferred one is unreachable.

However, adding several addresses does not guarantee faster resolution or correct failover if some of those servers are offline or belong to the wrong network.

Microsoft documents that the Windows DNS Client tries configured DNS servers according to its resolver behavior and waits for responses before moving to other servers.

An unreachable resolver can therefore introduce delays.

A list containing several old or inaccessible addresses may make applications appear slow even when a working resolver is available later in the list.

Inspect the DNS server list with ipconfig /all.

If you find addresses that do not belong to the current network, compare them with the router's DHCP settings or the organization's approved configuration.

Remove obsolete entries only after confirming they are not required for internal domains, VPN resolution, or failover.

Avoid combining a company DNS server with a public resolver without understanding the design.

Windows does not treat multiple DNS servers as a simple universal preference list in which every query is sent to whichever server gives the best answer.

A public resolver may not know private company records, while an internal resolver may be configured to enforce security or filtering policies.

Use the DNS servers approved for the network.

Investigate one domain

If only one website or domain fails, the resolver may be functioning correctly.

The domain could have incorrect DNS records, an expired registration, a broken delegation, or a recent DNS change that has not propagated through every resolver.

VPN

NordVPN

4.8
4.8

This NordVPN Review for 2026 covers its server network, no logs policy, security features, pricing tiers, and what you get for your money.

  • Massive server network globally
  • RAM only servers for privacy
  • Prices jump after first year
  • Fewer features in basic plan

A domain can also return NXDOMAIN if the requested name does not exist.

Start by testing the exact hostname rather than only the website's main domain.

For example, www.example.com and example.com can have different DNS records.

Run nslookup for each name and compare the results.

If one resolves and the other does not, the problem may concern a missing or incorrect record rather than the Windows computer.

Compare the response from the configured resolver with two independent public resolvers:

  • Run nslookup www.example.com to query the DNS server configured in Windows.
  • Run nslookup www.example.com 1.1.1.1 to query Cloudflare.
  • Run nslookup www.example.com 8.8.8.8 to query Google Public DNS.
  • Record the returned address or error from each query.
  • Repeat the test after some time if the domain has recently changed its DNS records.

If all resolvers return the same negative response, check the domain's authoritative DNS configuration or contact its administrator.

If only the local or provider resolver returns an outdated result, the issue may involve caching or that resolver's forwarding path.

Cloudflare's troubleshooting guidance recommends comparing results from its resolver with another public resolver when investigating name resolution problems.

Do not change your computer's DNS settings to repair a domain whose authoritative records are incorrect.

A public resolver cannot invent a missing A, AAAA, MX, or CNAME record.

The domain owner or DNS administrator must correct the record at the authoritative DNS provider.

Verify the repair

A successful DNS command is a useful sign, but verify the applications and network services that originally failed.

Test more than one domain and compare the result with the original error.

If the issue affected a company application, internal hostname, or VPN connection, test those services separately.

Complete the following verification checklist:

  • Run ipconfig /all and confirm that the active adapter has the correct DNS servers.
  • Run nslookup example.com and confirm that the resolver returns an address.
  • Test a second unrelated domain to rule out a single domain problem.
  • Open the affected websites in the browser that originally failed.
  • Test email, VPN, internal applications, and other services that rely on DNS.
  • Restart the computer if the repair required a network stack or driver change.
  • Record the change that restored access and retain the original settings for reference.

If the error returns, note whether it happens after sleep, a VPN connection, a network change, or a router restart.

A recurring failure after VPN connection suggests a different cause from a failure that affects every device at the same time.

The time of the incident, the DNS server address, and the output of nslookup can help an administrator identify whether the failure is local, upstream, or server side.

For advanced investigation, Microsoft recommends collecting diagnostic data from the affected DNS client and server while reproducing the failure.

Administrators can use Windows network tracing and DNS server logs to determine whether queries leave the client and whether the resolver receives and answers them.

This is more reliable than repeatedly changing settings when the failure occurs only under specific network conditions.

Frequently Asked Questions

Why does DNS fail after connecting to a VPN?
A VPN can replace the DNS servers assigned to the normal network adapter and route queries through company or VPN provider infrastructure. If the VPN DNS server is unreachable, incorrectly configured, or blocked by a firewall, domain lookups may fail while the VPN appears connected. Disconnect the VPN temporarily, if your organization's policy allows it, and repeat nslookup. If resolution returns after disconnection, report the VPN DNS configuration to the administrator rather than permanently bypassing its settings.
Can antivirus software block DNS requests?
Yes. Some security products inspect DNS traffic, filter malicious domains, or apply firewall rules that affect DNS queries. If the problem began after installing or updating an antivirus or endpoint security product, review its network protection logs and DNS filtering settings. Do not disable all protection as a permanent solution. Use the product's approved troubleshooting mode or ask the security administrator to confirm whether UDP or TCP port 53 traffic is being blocked.
Why does DNS work on mobile data but fail on Wi-Fi?
This usually points toward the router, internet provider, or DNS settings supplied by the Wi-Fi network. Mobile data uses a separate network connection and often a different DNS resolver, so it can resolve the same domain while the home or office network cannot. Compare the DNS response from the Wi-Fi connection with a public resolver, then test another device on that network. If several devices fail together, investigate the router or provider.
Does changing DNS improve internet speed?
Changing DNS can reduce the time required to resolve domain names if the original resolver is slow or unreliable. It does not increase the bandwidth supplied by the internet provider or repair poor Wi-Fi signal, packet loss, or an overloaded router. A faster lookup may make the first connection to a website feel more responsive, but the benefit depends on the resolver, network route, and existing cache. Compare query response times before and after the change.
Should I use public DNS on a company computer?
No, not without approval from the organization's IT administrator. Corporate networks may rely on internal DNS records for Active Directory, file servers, authentication, printers, and business applications. A public resolver such as 1.1.1.1 or 8.8.8.8 cannot normally resolve private company hostnames. It may also bypass approved filtering, logging, or security controls. Keep the assigned corporate DNS configuration unless the administrator authorizes a change.
Sources5

External pages are independent third-party sources. Desking App does not control or endorse their content and accepts no responsibility for it. Visiting them is at your own responsibility and risk.

Advertisement

Liked this? Get the next one in your inbox