This guide walks you through fixing the “DNS_PROBE_FINISHED_NO_INTERNET” error in Google Chrome. This error appears when Chrome cannot resolve a website’s address through your network’s DNS (Domain Name System) servers, even though your internet connection may otherwise appear active. The steps below cover the most common causes and solutions, from simple browser resets to system-level network commands.
What You’ll Need
- Administrator access to your computer (to run some commands and change network settings).
- Your router’s login credentials (usually printed on the router itself) if you need to restart it.
- A few minutes of time; most fixes take under five minutes.
Step-by-Step
- Check if the internet works on other devices. Open a browser on your phone or another computer. If those work, the problem is isolated to your current device or Chrome. If they also fail, your network or router is the issue—skip to step 6.
- Restart Chrome completely. Close all Chrome windows, then reopen it. If the error persists, type
chrome://net-internals/#dnsin the address bar, click “Clear host cache,” then restart Chrome again. - Flush your DNS cache (Windows). Press
Win + R, typecmd, and press Enter. In the command prompt, typeipconfig /flushdnsand press Enter. You should see “Successfully flushed the DNS Resolver Cache.” - Flush your DNS cache (macOS). Open Terminal (Applications > Utilities) and run
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Enter your password when prompted. - Change your DNS servers to a public provider. This bypasses your ISP’s potentially faulty DNS. For Windows: go to Control Panel > Network and Sharing Center > Change adapter settings. Right-click your active connection (Wi-Fi or Ethernet), select Properties, then select “Internet Protocol Version 4 (TCP/IPv4)” and click Properties. Choose “Use the following DNS server addresses” and enter
8.8.8.8and8.8.4.4(Google) or1.1.1.1and1.0.0.1(Cloudflare). Click OK and restart Chrome. On macOS: go to System Settings > Network, select your connection, click Details, then DNS, and add the same addresses. - Restart your router and modem. Unplug the power from both devices. Wait 30 seconds, plug the modem back in, wait for it to fully boot (lights stabilize), then plug in the router. Wait another minute, then try Chrome again.
- Disable Chrome’s built-in DNS client. In Chrome, go to Settings > Privacy and security > Security. Toggle off “Use secure DNS” (or “Always use secure DNS”). This forces Chrome to use your system’s DNS settings, which may resolve conflicts.
- Reset Chrome’s network settings. Go to Settings > Advanced > Reset and clean up > Restore settings to their original defaults. This disables extensions and resets flags, but keeps your bookmarks and passwords.
- Run Windows network diagnostics. In the command prompt (as administrator), type
netsh winsock resetand press Enter, thennetsh int ip resetand press Enter. Restart your computer. - Check your hosts file. On Windows, navigate to
C:\Windows\System32\drivers\etcand open the file named “hosts” with Notepad. Ensure there are no lines that start with an IP address followed by the site you’re trying to visit (except “127.0.0.1 localhost”). On macOS, the file is at/etc/hosts. Delete any suspicious entries and save.
Common Mistakes
- Skipping the reboot after changing DNS settings. Some changes only take effect after a full system restart, not just a browser restart.
- Typing the DNS addresses incorrectly. A single wrong digit (like 8.8.8.8 vs 8.8.8.9) will cause the same error. Double-check each number.
- Flushing DNS without administrator rights. On Windows, the command prompt must be run as administrator, or the flush will fail silently.
- Assuming the error means no internet at all. The error can appear even when you can access some sites; it’s specifically a DNS resolution failure, not a general connectivity loss.
- Editing the hosts file incorrectly. Adding a line with a space instead of a tab, or saving it as .txt, will break the file. Save as “All files” with no extension.
Tips
- Use a reliable public DNS like Google (8.8.8.8) or Cloudflare (1.1.1.1) permanently; they are often faster and more reliable than ISP defaults.
- If the error only occurs on one website, try accessing it via a different browser or incognito mode to rule out cache or extension issues.
- Keep your router firmware updated. Log into your router’s admin panel (usually 192.168.1.1 or 192.168.0.1) and check for firmware updates.
- Consider using a VPN if your ISP’s DNS is frequently unreliable, but note that a VPN can also cause the error if its servers are down.
Troubleshooting
If you’ve tried all the steps and the error persists:
- Try a different browser. If Edge or Firefox works, the problem is Chrome-specific—try reinstalling Chrome completely (uninstall, then download fresh from google.com/chrome).
- Check for malware. Some malware modifies DNS settings or the hosts file. Run a full system scan with your antivirus or Windows Defender.
- Test with a wired connection. If you’re on Wi-Fi, connect via Ethernet cable. If it works, your Wi-Fi adapter or router’s wireless settings are the issue.
- Update your network drivers. On Windows, go to Device Manager, expand “Network adapters,” right-click your adapter, and select “Update driver.” On macOS, update via System Settings > General > Software Update.
- Contact your ISP. If the error occurs on all devices and persists after router restart, your ISP may be having an outage or DNS issue on their end.
Frequently Asked Questions
What does DNS_PROBE_FINISHED_NO_INTERNET actually mean?
It means Chrome sent a request to your DNS server to translate a website name (like example.com) into an IP address, but the server didn’t respond or returned an invalid result. Your internet connection might be fine, but the “phonebook” that maps names to addresses is unreachable.
Will changing DNS to 8.8.8.8 fix the error permanently?
In most cases, yes, if the root cause is your ISP’s DNS servers being down or slow. However, if the issue is due to malware, a broken network stack, or router problems, you may need to combine this with other fixes like flushing DNS or resetting the router.
Why does the error appear only in Chrome but not in other browsers?
Chrome has its own DNS cache and secure DNS feature. If those are corrupted or conflicting with your system’s DNS, you’ll see the error only in Chrome. Clearing Chrome’s cache or disabling secure DNS usually resolves it.
Can a VPN cause this error?
Yes. A VPN routes your traffic through its own DNS servers. If those servers are unreachable or misconfigured, you’ll get this error. Try disconnecting the VPN and see if the error disappears.
Is it safe to edit the hosts file?
Yes, if you’re careful. The hosts file is a local override for DNS. As long as you only remove suspicious lines and don’t alter the default 127.0.0.1 localhost entry, it’s safe. Always back up the file before editing.
How often should I flush my DNS cache?
Only when you encounter DNS-related errors. Flushing daily is unnecessary and can slightly slow down browsing because your computer has to re-resolve all domain names. It’s a troubleshooting step, not a maintenance routine.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Ubuntu Printer Detected But Won’t Print: Fix
- Autoplay Not Working on Windows 11? Fix It
- Edit Messages on iPhone & View Edit History
- How to Clean Rust Off Chrome Dinette Legs
- How to Add Another Account on Telegram
- Prepare Your PC for a Major Windows Upgrade