When Websites Will Not Load: A Practical DNS Troubleshooting Guide
DNS errors occur when a device cannot translate a website name, such as example.com, into the IP address needed to reach it. They may affect one site, every browser, or every device on a home or office network. This guide explains how to identify the scope of the problem, distinguish DNS failures from general connectivity issues, test name resolution, restart the right equipment, clear local caches, review VPN and proxy settings, and choose reliable public DNS resolvers when appropriate. It also covers router-level checks, security considerations, and signs that an internet service provider or network administrator should be contacted.
A DNS error can make the internet appear broken even when your connection is otherwise working. You may be able to open an app, receive email, or reach one website by an old bookmark while other pages show messages such as “DNS_PROBE_FINISHED_NXDOMAIN,” “server DNS address could not be found,” or “this site cannot be reached.” DNS, short for Domain Name System, is the service that converts a human-readable address such as www.example.com into the numeric IP address that networks use. Finding where that lookup fails is the fastest route to a fix.
Understand what a DNS error is telling you
When you enter a domain name, your device asks a DNS resolver for the matching IP address. The resolver may answer from cache or query other authoritative DNS servers. A failure can happen on the device, in the browser, on the router, at a chosen DNS provider, or with the domain’s own DNS records.
It is important not to assume that every loading error is DNS-related. A site can fail because its web server is offline, a firewall is blocking it, the browser has a bad extension, or your connection has dropped entirely. The scope of the failure provides useful clues:
- One domain fails on all devices: the site or its DNS records may be having an external outage.
- Many domains fail on one device: inspect that device’s DNS, VPN, proxy, browser, and security software settings.
- Many devices fail on the same Wi-Fi network: the router, ISP connection, or router DNS configuration is more likely involved.
- Wi-Fi fails but mobile data works: compare the local network’s DNS path with the mobile carrier’s path.
Start with quick, low-risk checks
Before changing network settings, confirm that the problem is repeatable. Try two or three well-known domains, then open the same address in a private browsing window or another browser. A private window can reveal whether cookies, extensions, or cached browser data are contributing.
- Check whether another device on the same network can open the affected website.
- Turn Wi-Fi off and test using cellular data, if available.
- Restart the browser and temporarily disable VPN, proxy, or content-filtering extensions.
- Restart your computer or phone if the problem remains isolated to that device.
- Power-cycle the modem and router: unplug them, wait about 30 seconds, reconnect the modem first, then the router.
If the issue begins immediately after installing a VPN, endpoint security product, parental-control service, or custom network profile, reverse that recent change first. These tools can redirect DNS requests intentionally, and a broken configuration can prevent normal lookups.
Test name resolution instead of guessing
A simple command-line lookup can separate DNS trouble from a browser issue. On Windows, open Command Prompt and run nslookup example.com. On macOS or Linux, Terminal users can run nslookup example.com or dig example.com if the tool is installed. Replace example.com with a domain that is failing.
A successful response normally shows one or more IP addresses. A timeout, “server failed,” or “non-existent domain” response is meaningful, but interpret it carefully. “Non-existent domain” may be correct if the address was typed incorrectly or the domain truly has no record.
| Test result | Likely meaning | Best next action |
|---|---|---|
| Sites work on mobile data but not home Wi-Fi | Local router, ISP path, or Wi-Fi DNS issue | Restart network equipment and review router DNS settings |
| Only one browser fails | Browser cache, extension, proxy, or secure-DNS setting | Use a private window, disable extensions, and reset browser network settings |
nslookup times out for many domains | Configured resolver is unreachable or blocked | Check VPN/firewall settings or test a reputable public resolver |
| Lookup succeeds but the page still will not open | Not necessarily a DNS problem | Check the site status, browser errors, HTTPS, and general connectivity |
| All devices on the network fail | Router, modem, ISP, or network-wide filtering issue | Restart equipment and contact the ISP or network administrator if it persists |
Clear cached DNS information
Devices and browsers retain DNS answers temporarily to improve performance. Usually this is helpful, but stale entries can keep directing you to an old or unreachable address after a site changes hosting. Clearing the operating system cache is safe; it does not delete personal files or browser passwords.
Windows, macOS, and browser caches
On Windows, open Command Prompt as appropriate for your environment and run ipconfig /flushdns. You should receive a confirmation that the DNS Resolver Cache was successfully flushed. On macOS, the exact command can vary by release, but current versions commonly use sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal. You will be asked for an administrator password.
Then close and reopen the browser. If only one site remains problematic, clear that browser’s cached data for the site or test from a private window before performing a full browser reset. A full reset can remove useful preferences and signed-in sessions.
Review DNS settings on the device and router
Most home networks obtain DNS servers automatically from the router, which in turn may receive them from the ISP. Automatic settings are normally the simplest choice. However, if the ISP-provided resolver is unavailable or unreliable, testing a recognized public DNS service can help identify the cause.
Common choices include Cloudflare DNS at 1.1.1.1 and 1.0.0.1, Google Public DNS at 8.8.8.8 and 8.8.4.4, and Quad9 at 9.9.9.9. Enter a primary and secondary address only in the DNS fields; do not change your IP address, subnet mask, or gateway unless you understand the network design.
Changing DNS can improve resolver availability, but it does not repair a failed internet connection, a blocked site, or an outage at the website itself. Treat it as a diagnostic step and a configuration choice, not a universal cure.
On Windows, DNS settings are generally available through Settings under Network & internet, then the active Wi-Fi or Ethernet connection, where you can edit DNS server assignment. On macOS, use System Settings, Network, select the active connection, then open Details and DNS. On phones, network options differ by manufacturer; changing router DNS is often more consistent for an entire household.
Check secure DNS, VPNs, proxies, and filtering
Modern browsers may use encrypted DNS, often called Secure DNS or DNS over HTTPS. This can improve privacy on untrusted networks, but it may conflict with workplace filtering, family safety controls, captive portals, or a DNS service required by an organization. In your browser’s privacy or security settings, temporarily switch Secure DNS to the default provider or turn it off for a test. Restore the setting if it was not the cause.
Also inspect these potential interceptors:
- A VPN client with its own DNS leak-protection feature.
- Manual proxy settings left behind by old software or a workplace configuration.
- Antivirus web shields or firewall rules that scan encrypted traffic.
- Router parental controls, ad-blocking DNS services, or custom blocklists.
- Hotel, airport, school, or office networks that require you to complete a sign-in page.
On a public Wi-Fi network, open a non-sensitive website to trigger the sign-in portal. Avoid entering passwords or payment information until you confirm that the network is legitimate and the connection is protected by HTTPS.
Know when the fault is outside your network
If several independent networks show the same result for one domain, the problem may be with that domain’s DNS hosting or web infrastructure. Waiting for the site operator to correct it is usually the only appropriate response. Do not try to bypass access restrictions or alter hosts files to reach a service unless you own the system or have explicit authorization.
Contact your ISP when every device loses access, the router cannot obtain a working connection after a proper restart, or DNS servers assigned automatically are consistently unreachable. In an office, school, or managed network, contact the administrator instead of changing DNS settings; organization-wide policies may be deliberate and changes can interfere with security controls.
