DNS Address Could Not Be Found: 12 Proven Fixes That Actually Work

Seeing “DNS address could not be found” usually means your browser cannot translate a website name, such as example.com, into the numerical IP address needed to load it. The problem may come from your device, router, DNS provider, browser cache, VPN, firewall, or the website’s own DNS records. The good news is that most cases are fixable without advanced technical skills if you work through the causes methodically.

TLDR: Start by checking whether the website works on another device or network, then restart your router and clear your DNS cache. In many support cases, DNS errors are resolved by basic steps such as switching DNS servers or flushing cached DNS records; for example, changing from an unstable ISP DNS server to Google DNS or Cloudflare DNS can restore access within minutes. If one site fails but others work, the issue may be with that website’s domain records rather than your computer.

What the Error Really Means

DNS, or Domain Name System, acts like the internet’s address book. When DNS lookup fails, your browser cannot find the server behind the domain name. In Google Chrome, this often appears as ERR_NAME_NOT_RESOLVED or “DNS address could not be found.” Other browsers may phrase it differently, but the underlying issue is similar: the domain name is not resolving correctly.

Before making major changes, confirm the scope of the problem. Ask yourself: does it happen on one website or every website? Does it happen only on one device? Does mobile data work while Wi-Fi does not? These answers help identify the most likely fix.

12 Proven Fixes That Actually Work

  1. Check the website address carefully

    A simple typo is one of the easiest causes to miss. Make sure the domain is spelled correctly and that you are not using an outdated bookmark. For example, typing gogle.com instead of google.com may lead to a DNS lookup failure or an unrelated domain.

  2. Test the site on another device or network

    Open the same website on your phone using mobile data, not Wi-Fi. If it works there, the issue is likely with your computer, router, DNS settings, or local network. If it does not work anywhere, the website itself may have DNS or hosting problems.

  3. Restart your router and modem

    Unplug your router and modem from power, wait at least 30 seconds, then plug them back in. This clears temporary connection problems and forces your network equipment to re-establish DNS and internet connectivity. It sounds basic, but it is often effective.

  4. Flush your DNS cache

    Your computer stores DNS results to speed up browsing. If those stored records are outdated or corrupted, DNS errors can appear even when the website is working normally.

    On Windows, open Command Prompt as administrator and run:

    ipconfig /flushdns

    On macOS, open Terminal and use the appropriate command for your version. A common command is:

    sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

    After flushing DNS, close and reopen your browser.

  5. Clear your browser cache and cookies

    Browsers store site data, redirects, and cached network information. If the error appears only in one browser, clearing cached data can help. In Chrome, go to Settings > Privacy and security > Clear browsing data, then clear cached images/files and cookies. Restart the browser afterward.

  6. Try a different browser

    If Chrome shows the error, test the same website in Firefox, Edge, or Safari. If the site works elsewhere, the problem may be browser-specific. Extensions, cached DNS data, or experimental browser settings can interfere with name resolution.

  7. Disable browser extensions temporarily

    Ad blockers, privacy extensions, antivirus add-ons, and proxy tools can block or reroute DNS requests. Disable extensions one by one, then reload the page. If the website starts working after disabling an extension, remove it or adjust its settings.

Image not found in postmeta

  1. Change your DNS servers

    Your internet provider’s DNS servers may be slow, outdated, or temporarily unavailable. Switching to a reliable public DNS provider is one of the most effective fixes.

    Common options include:

    • Google DNS: 8.8.8.8 and 8.8.4.4
    • Cloudflare DNS: 1.1.1.1 and 1.0.0.1
    • OpenDNS: 208.67.222.222 and 208.67.220.220

    After changing DNS settings, restart your browser and test the website again. For many users, this resolves the error immediately when the cause is an unreliable ISP DNS resolver.

  2. Reset TCP/IP and network settings

    Corrupted network configuration can prevent proper DNS resolution. On Windows, open Command Prompt as administrator and run:

    netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

    Restart your computer after running these commands. This resets key networking components and often fixes persistent connection issues.

  3. Disable VPN, proxy, or custom DNS apps

    VPNs and proxies can route DNS requests through external servers. If those servers are blocked, overloaded, or misconfigured, websites may fail to resolve. Temporarily disconnect your VPN, turn off proxy settings, and disable third-party DNS filtering apps. If the site loads afterward, update the app or switch to a more reliable server location.

  4. Check firewall and antivirus settings

    Security software can block domains, DNS traffic, or browser access. This is more common in corporate environments or on devices with strict web protection settings. Temporarily disable web filtering features only long enough to test the site. If that fixes the issue, create a safe exception rather than leaving protection disabled.

  5. Verify the website’s DNS records

    If you own the website, the problem may be on the domain side. Check whether the domain has valid A, AAAA, or CNAME records. Also confirm that the nameservers are correct and that the domain has not expired. DNS changes can take time to propagate, often from a few minutes up to 24–48 hours, depending on TTL settings and registrar behavior.

Image not found in postmeta
domain

How to Know Where the Problem Is

A quick pattern check can save time. If all websites fail, focus on your router, ISP, DNS servers, or device network settings. If only one website fails, test it from mobile data or an online DNS checker. If the site works on other networks but not yours, local DNS caching or ISP-level DNS problems are likely.

If you manage the affected domain, use tools such as DNS lookup, WHOIS, and nameserver checks to confirm that your records are public and correct. A missing A record or incorrect nameserver can make a website effectively invisible even when the hosting server is working.

When to Contact Support

Contact your internet provider if no websites resolve after trying router restart, DNS change, and network reset. Contact your hosting provider or domain registrar if only your own domain fails and DNS records appear incorrect. When reporting the issue, include the exact error message, affected domain, device type, network used, and fixes already attempted. This reduces back-and-forth and helps support teams identify the cause faster.

Final Advice

The “DNS address could not be found” error is frustrating, but it is usually not permanent. Work from the simplest checks toward deeper network changes: verify the URL, test another network, restart hardware, flush DNS, clear browser data, then change DNS servers. If the issue is website-specific, investigate the domain’s DNS records. A careful step-by-step approach is the most reliable way to restore access without making unnecessary changes.

Have a Look at These Articles Too

Published on July 26, 2026 by Ethan Martinez. Filed under: .

I'm Ethan Martinez, a tech writer focused on cloud computing and SaaS solutions. I provide insights into the latest cloud technologies and services to keep readers informed.