Setup and Configuration

Why Does My Wifi Not Work? DNS Errors Uncovered

Introduction If you have ever stared at your screen wondering Why Does My Wifi Not Work?, you are not alone. One of the most common and confusing culprits behind a “connected but no internet” situation is a DNS error. Your device may show full WiFi bars, yet p

HowToFixWiFi

Introduction

If you have ever stared at your screen wondering Why Does My Wifi Not Work?, you are not alone. One of the most common and confusing culprits behind a “connected but no internet” situation is a DNS error. Your device may show full WiFi bars, yet pages refuse to load, apps time out, and streaming services spin forever. In most cases, the WiFi radio itself is fine; the problem lives one layer deeper, in how your device translates website names into the numeric addresses that networks actually use.

This guide unpacks DNS errors in plain language. You will learn what DNS is, how to recognize the most common DNS-related messages, and exactly how to fix them on Windows, macOS, Android, iOS, and your router. Whether you are a home user or a small office administrator, the steps below will walk you through diagnosis and repair from the simplest reboot to advanced network resets.

Table of Contents

What Is DNS and Why Does It Matter?

DNS stands for Domain Name System. Think of it as the internet’s phone book. When you type a web address such as example.com, your device does not actually know where that site lives. It sends a request to a DNS server, which replies with the IP address of the server hosting that site. Only then can your browser connect and load the page.

Every time you open an app, check email, or stream a video, a DNS lookup happens behind the scenes. If that lookup fails, your device cannot find the destination even though your WiFi connection is technically active. That gap between “connected to WiFi” and “able to reach the internet” is exactly why so many people ask Why Does My Wifi Not Work? when the real issue is name resolution.

DNS servers are usually assigned automatically by your internet service provider. However, you can override them with public alternatives that are often faster and more reliable. Understanding this simple concept makes every troubleshooting step that follows much easier.

Why Does My Wifi Not Work? Common DNS Error Symptoms

DNS problems rarely announce themselves clearly. Instead, they masquerade as generic connectivity failures. Learning to spot the pattern will save you hours of guessing.

  • Websites load partially or not at all, while the WiFi icon shows full signal.
  • Some apps work (for example, a game with a cached connection) while browsers fail.
  • Error messages mention DNS, server not found, or name resolution.
  • Switching to mobile data on a phone immediately fixes the issue.
  • Pinging a website by name fails, but pinging its IP address succeeds.

That last test is the gold standard. If you can reach 8.8.8.8 but not google.com, you have a DNS problem, not a WiFi problem. This distinction is crucial when deciding how to proceed.

DNS Server Not Responding

“DNS server not responding” is one of the most common messages Windows and macOS users see. It means your device sent a lookup request and never received an answer. Causes range from a temporary glitch in your router to an outage at your ISP’s DNS server.

Typical triggers include:

  • Router firmware hanging after days of uptime.
  • An overloaded or misconfigured DNS server at your ISP.
  • Incorrect manual DNS settings entered previously.
  • Firewall or antivirus software blocking port 53.
  • VPN software intercepting and mishandling DNS queries.

Because the root cause varies, the fix is a process of elimination rather than a single magic step.

DNS Probe Finished NXDOMAIN

NXDOMAIN stands for Non-Existent Domain. It means the DNS server successfully responded, but it said the domain you requested does not exist. In Chrome, this often appears as “DNS_PROBE_FINISHED_NXDOMAIN.”

Sometimes the domain genuinely does not exist, especially if you mistyped the address. But when the error appears for well-known sites, the cause is usually local: cached incorrect data, a hosts file entry, or a DNS server returning wrong information.

Flushing the DNS cache and clearing browser cache resolves most NXDOMAIN cases. If the problem persists across all browsers, check your system’s hosts file for accidentally added entries that redirect or block domains.

DNS_PROBE_FINISHED_BAD_CONFIG

This error points to a configuration problem rather than a missing domain. Your device’s network settings are inconsistent, perhaps because of a partial VPN disconnect, a corrupted network profile, or conflicting IPv4 and IPv6 settings.

Common fixes include resetting the network adapter, releasing and renewing the IP address, and ensuring DNS is set to obtain automatically or to a valid public server. On mobile devices, toggling airplane mode and reconnecting often clears the bad configuration state.

Other Common DNS Error Messages

Beyond the big three, you may encounter several related messages:

  • ERR_NAME_NOT_RESOLVED: The browser could not translate the hostname.
  • DNS_PROBE_FINISHED_NO_INTERNET: DNS is working but broader connectivity is down.
  • Server DNS address could not be found: A Windows-specific phrasing of a lookup failure.
  • Could not resolve host: Common in command-line tools and Linux systems.

Each of these ultimately traces back to the same chain: your device, the DNS server, the domain’s authoritative servers, and the network path between them. Diagnosing which link broke is the heart of troubleshooting.

How to Fix DNS Errors: Step-by-Step

Work through these steps in order. Most issues resolve within the first three.

Step 1: Restart Your Router and Device

Unplug your router for 30 seconds, then plug it back in. Restart your computer or phone as well. This clears temporary memory states and forces a fresh DHCP lease and DNS assignment.

Step 2: Flush the DNS Cache

On Windows, open Command Prompt as administrator and run:

ipconfig /flushdns
ipconfig /release
ipconfig /renew

On macOS, run in Terminal:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

On Android and iOS, toggling airplane mode for 10 seconds effectively clears cached DNS entries.

Step 3: Change Your DNS Servers

Switching to a reliable public DNS provider often fixes recurring errors. Use the comparison table below to choose. On Windows, go to Network Connections, properties of your adapter, IPv4, and enter preferred and alternate DNS. On macOS, use System Settings, Network, Details, DNS.

Step 4: Reset the Network Adapter

If configuration is corrupted, reset the adapter. On Windows, run:

netsh winsock reset
netsh int ip reset

Then reboot. On macOS, remove the network service in System Settings and re-add it.

Step 5: Check Firewall, Antivirus, and VPN

Temporarily disable VPN software and security suites that filter DNS. If connectivity returns, re-enable them one at a time to identify the culprit, then whitelist DNS traffic on port 53 and 443.

Step 6: Update Router Firmware

Log into your router admin panel and check for firmware updates. Outdated firmware can mishandle DNS forwarding, especially on older models.

Comparison of Popular Public DNS Providers

Choosing the right DNS server affects speed, privacy, and reliability. Here is a quick comparison.

Provider Primary DNS Secondary DNS Strengths Best For
Google Public DNS 8.8.8.8 8.8.4.4 Speed, global coverage General use
Cloudflare 1.1.1.1 1.0.0.1 Privacy, low latency Privacy-focused users
Quad9 9.9.9.9 149.112.112.112 Malware blocking Security-conscious users
OpenDNS 208.67.222.222 208.67.220.220 Content filtering Families, businesses

For most home users, Cloudflare or Google provides an immediate improvement over ISP defaults. If you have children or need filtering, OpenDNS is a strong choice.

Advanced Troubleshooting

If basic steps fail, dig deeper.

  • Test with nslookup: Run nslookup google.com 8.8.8.8 to query a specific server directly. If it fails, the issue is network path or firewall, not DNS configuration.
  • Check IPv6: Disable IPv6 temporarily if your ISP’s IPv6 DNS is misbehaving. Some routers advertise broken IPv6 DNS addresses.
  • Inspect the hosts file: On Windows, open C:\Windows\System32\drivers\etc\hosts. Remove any suspicious lines.
  • Factory reset the router: As a last resort, reset to factory defaults and reconfigure. Back up settings first.
  • Test another device: If only one device is affected, the problem is local. If all devices fail, the router or ISP is at fault.

Tips and Best Practices

  • Set a reliable public DNS on your router so every device benefits automatically.
  • Keep router firmware updated to avoid known DNS-forwarding bugs.
  • Use a UPS for your router and modem to prevent corruption from sudden power loss.
  • Document your working settings before experimenting.
  • Avoid editing the hosts file unless you understand the consequences.
  • Restart networking equipment monthly as preventive maintenance.

When to Contact Your ISP

If multiple devices fail on multiple DNS servers, and pinging IP addresses also fails, the issue is likely upstream. Contact your ISP when:

  • Outages are reported in your area.
  • Your modem cannot sync or shows red lights.
  • DNS works only intermittently despite correct configuration.
  • Your account or service has been suspended or throttled.

Provide your ISP with the troubleshooting steps you already tried; this speeds up resolution and prevents redundant suggestions.

Frequently Asked Questions

Why Does My Wifi Not Work even though it says connected?

Being connected to WiFi only means your device joined the local network. If DNS or internet routing fails, you will have no actual access. Check whether you can ping an IP address; if yes, it is a DNS issue.

Will changing DNS speed up my internet?

It can reduce latency for lookups and improve reliability, but it will not increase your bandwidth. A faster DNS mainly makes pages start loading quicker.

Is it safe to use public DNS servers?

Yes, reputable providers like Cloudflare and Google are safe. Some even improve privacy by not logging queries. Avoid unknown third-party DNS addresses.

Why do DNS errors happen only on one device?

That usually points to device-specific settings, a VPN, a corrupted cache, or security software. Resetting that device’s network settings typically resolves it.

How often should I flush DNS?

Only when troubleshooting. Routine flushing is unnecessary and can briefly slow lookups while the cache rebuilds.

Conclusion

When you ask Why Does My Wifi Not Work?, the answer is often hiding in DNS rather than in your WiFi signal. By understanding how name resolution works, recognizing the common error messages, and following a structured troubleshooting process, you can resolve most issues in minutes. Start with a reboot and cache flush, move to public DNS servers if needed, and escalate to adapter resets or ISP contact only when simpler fixes fail. With the steps and comparison table in this guide, you now have a complete toolkit for keeping your connection healthy and your browsing uninterrupted.