Few things are more frustrating than clicking a website and seeing the message “DNS address could not be found” instead of the page you expected. This error usually means your browser cannot translate a website name, such as example.com, into the numeric IP address needed to load it. The good news is that the problem is often local, temporary, and fixable with a few clear steps.
TLDR: The “DNS address could not be found” error usually happens when your device, browser, router, or DNS provider cannot resolve a website’s domain name. Start by checking the website and your internet connection, then clear your browser and DNS cache. If that does not work, change your DNS servers, restart your router, or reset your network settings.
What Does the Error Mean?
DNS stands for Domain Name System. Think of it as the internet’s phonebook. When you type a website address into your browser, DNS finds the matching IP address so your device knows where to go. If that lookup fails, browsers such as Chrome may show messages like “DNS address could not be found”, “ERR_NAME_NOT_RESOLVED”, or “This site can’t be reached.”
The cause may be as simple as a mistyped URL, or it may involve cached data, incorrect DNS settings, router issues, firewall restrictions, or a temporary outage from the website itself.
Step 1: Check the Website Address
Before changing settings, confirm that the address is correct. A small typo can trigger the error instantly.
- Look for misspelled words in the domain name.
- Check whether the site uses .com, .org, .net, or another extension.
- Remove extra spaces or unusual characters from the address bar.
- Try searching for the website name in a search engine instead of typing the URL manually.
If the site loads from search results, the issue was likely the address you entered.
Step 2: See If the Website Is Down
Sometimes the problem is not your device at all. The website’s server or DNS records may be temporarily unavailable. Try opening the same site on another device or network, such as your mobile phone using cellular data.
You can also check a website status service by searching “is this website down” and entering the domain. If the site is down for everyone, the only real fix is to wait until the owner resolves the issue.
Step 3: Restart Your Browser and Device
It sounds basic, but restarting often clears temporary problems. Close your browser completely and reopen it. If that does not help, restart your computer, phone, or tablet.
This refreshes network connections, clears stuck processes, and may resolve temporary DNS or browser conflicts. If you have many tabs, extensions, or background apps running, a restart can be surprisingly effective.
Step 4: Restart Your Router and Modem
Your router stores connection data and can occasionally get stuck using outdated DNS information. Restarting it forces a fresh connection to your internet service provider.
- Unplug your router and modem from power.
- Wait at least 30 seconds.
- Plug the modem back in first, if separate.
- Wait until its lights stabilize.
- Plug the router back in and wait for Wi Fi to return.
After reconnecting, try loading the website again. This step fixes many home network related DNS errors.
Step 5: Clear Your Browser Cache
Browsers store cached files to make websites load faster. However, old or corrupted cache data can interfere with domain lookup or page loading.
In Google Chrome, you can clear the cache by going to:
- Settings
- Privacy and security
- Clear browsing data
- Select Cached images and files
- Click Clear data
You do not always need to delete saved passwords or browsing history. Start with cached files first, then test the website again.
Step 6: Flush the DNS Cache
Your operating system also stores DNS lookup results. If those records are outdated or broken, flushing the DNS cache can force your device to request fresh information.
On Windows
- Open the Start menu.
- Type cmd.
- Right click Command Prompt and choose Run as administrator.
- Enter this command:
ipconfig /flushdns - Press Enter.
You should see a message saying the DNS Resolver Cache was successfully flushed.
On macOS
Open Terminal and enter the command appropriate for your macOS version. For many recent versions, this works:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Enter your administrator password if prompted, then test the website again.
Step 7: Change Your DNS Servers
If your internet provider’s DNS servers are slow, overloaded, or misconfigured, switching to a public DNS service can solve the issue. Popular options include:
- Google Public 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
On Windows, go to Settings > Network and Internet > your connection > DNS server assignment, then choose manual DNS settings. On macOS, go to System Settings > Network > your active connection > Details > DNS.
After changing DNS servers, restart your browser and try the website again.
Step 8: Disable VPN, Proxy, or Security Software Temporarily
VPNs, proxy servers, firewalls, and antivirus tools can sometimes block DNS requests or route them incorrectly. If you use a VPN, disconnect it and reload the site. If you use a proxy, temporarily turn it off in your network settings.
You can also briefly disable web protection features in your security software to test whether they are causing the problem. Do not leave protection disabled permanently; this is only a troubleshooting step.
Step 9: Reset Network Settings
If nothing has worked so far, resetting your network settings may clear deeper configuration issues.
On Windows, open Command Prompt as administrator and run these commands one at a time:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Restart your computer afterward.
On macOS, you can remove and re add your Wi Fi connection in network settings, or create a new network location. This forces macOS to rebuild network preferences.
Step 10: Contact Your ISP or Website Owner
If the error happens across multiple devices on the same network, your internet service provider may be having DNS problems. Contact support and ask whether there are known outages or DNS issues in your area.
If only one specific website fails and everyone else can access it, the site may have incorrect DNS records. In that case, the website owner or hosting provider must fix the domain configuration.
Final Thoughts
The “DNS address could not be found” error looks technical, but the fix is usually straightforward. Start with simple checks such as confirming the URL, restarting your browser, and rebooting your router. Then move on to clearing caches, flushing DNS, and changing DNS servers. By working through these steps in order, you can quickly narrow down whether the issue is with your device, your network, your DNS provider, or the website itself.