sodcalculator

10 Tech How-To

How to Fix DNS Probe Started in Chrome

Guide 10-47830 · Updated · Step by step

DNS_PROBE_STARTED is a Chrome error that appears when the browser cannot resolve a website’s address, often due to network, DNS, or cache issues. This guide walks you through practical fixes to restore your connection and get back online quickly.

What You’ll Need

  • Access to your router (usually via a web browser)
  • Administrator rights on your computer (for some steps)
  • A stable internet connection (even if it’s spotty)

Step-by-Step

  1. Check if the problem is site-specific. Try opening a different website, like example.com or a search engine. If other sites work, the issue is likely with the specific site, not your connection.
  2. Restart your router and modem. Unplug both devices, wait 30 seconds, plug the modem back in, wait for it to fully boot, then plug in the router. Once the lights stabilize, try Chrome again.
  3. Clear Chrome’s DNS cache. In Chrome’s address bar, type chrome://net-internals/#dns and press Enter. Click the “Clear host cache” button. Then go to chrome://net-internals/#sockets and click “Flush socket pools.” Restart Chrome.
  4. Flush your system’s DNS cache.
    • Windows: Open Command Prompt as Administrator and run ipconfig /flushdns.
    • macOS: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder (you’ll need your password).
    • Linux: Depending on your distro, run sudo systemd-resolve --flush-caches or sudo service network-manager restart.
  5. Change your DNS server. If the default DNS (usually your ISP’s) is failing, switch to a public one like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1).
    • Windows: Go to Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings. Right-click your connection, choose Properties, select “Internet Protocol Version 4 (TCP/IPv4)”, click Properties, then choose “Use the following DNS server addresses” and enter the new DNS.
    • macOS: Go to System Settings > Network, select your connection, click Details, go to DNS, and add the new servers.
    • Router: Log into your router’s admin page (usually 192.168.1.1 or 192.168.0.1), find the DNS settings, and change them there.
  6. Disable Chrome’s built-in DNS. Go to Chrome Settings > Privacy and security > Security, and turn off “Use secure DNS” (or “DNS over HTTPS”). This can help if the secure DNS service is causing the issue.
  7. Reset Chrome flags. Type chrome://flags in the address bar, press Ctrl+F (or Cmd+F) and search for “DNS”. Reset any DNS-related flags to “Default” (or “Disabled”). Then restart Chrome.
  8. Run a network troubleshooter.
    • Windows: Go to Settings > Network & Internet > Status, and click “Network troubleshooter.”
    • macOS: Go to System Settings > Network, and click “Assist me” or “Diagnostics.”
  9. Restart your computer. A full restart can clear temporary network glitches that persist even after flushing caches.

Common Mistakes

  • Only flushing Chrome’s cache, not the system’s. The system DNS cache is separate and often the culprit.
  • Changing DNS on the wrong adapter. If you have multiple network adapters (Wi-Fi and Ethernet), make sure you change the one you’re actually using.
  • Forgetting to restart after changing DNS. Some settings only take effect after a restart of the browser or computer.
  • Typing the DNS server address incorrectly. A single typo (like 8.8.8.9) will break DNS entirely.

Tips

  • Use a DNS checker website (like dnschecker.org) to see if the site is down for everyone or just you.
  • Try a different browser (Firefox, Edge) to see if the issue is Chrome-specific.
  • Disable VPN or proxy extensions temporarily, as they can interfere with DNS resolution.
  • Keep your router’s firmware updated to avoid DNS bugs.

Troubleshooting

If the error persists after trying all steps:

  • Check for malware. Run a full system scan with your antivirus or Windows Defender. Malware can hijack DNS settings.
  • Check your hosts file. On Windows, it’s at C:\Windows\System32\drivers\etc\hosts; on macOS/Linux, /etc/hosts. Look for any lines that block the site you’re trying to reach (they’d have the site’s name after an IP). Remove them if found.
  • Reset Chrome settings. Go to Settings > Advanced > Reset and clean up > Restore settings to their original defaults. This will disable extensions and clear some caches.
  • Reinstall Chrome. Uninstall Chrome, then download and install the latest version from Google’s official site. Make sure to back up bookmarks and passwords first.
  • Contact your ISP. If other devices on the same network also fail to resolve DNS, the problem might be on your ISP’s side. Call them and ask if there’s a known outage.

Frequently Asked Questions

What does DNS_PROBE_STARTED mean?

It means Chrome started a DNS lookup but didn’t get a response, so it aborted the connection. It’s essentially a “can’t find the website’s IP address” error.

Will clearing my DNS cache lose my browsing history?

No, the DNS cache only stores IP addresses for domain names. It doesn’t affect your history, bookmarks, or passwords.

Is changing my DNS server safe?

Yes, using a public DNS like Google or Cloudflare is generally safe and often faster. Just make sure you enter the correct IP addresses.

Why does this error happen on only one device?

If only one device fails, it’s likely a local cache issue or a misconfigured network setting on that device. The fixes above should resolve it.

Can a VPN cause this error?

Yes, VPNs can interfere with DNS resolution. Try disconnecting from the VPN and see if the error goes away.

How long does it take to fix?

Most fixes take under 10 minutes. The quickest ones (flushing caches, changing DNS) often solve it immediately.

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

The whole Tech How-To bed →