How To Fix the DNS_PROBE_STARTED Error [Step-by-Step Guide]

If you’ve ever browsed the internet and suddenly seen the DNS_PROBE_STARTED error, you know how frustrating it can be. This error often appears in browsers like Google Chrome and indicates that your device is having trouble connecting to the website via DNS (Domain Name System).

While it might sound technical, fixing this issue is usually straightforward. In this step-by-step guide, we’ll explain what the DNS_PROBE_STARTED error is, why it occurs, and how you can resolve it quickly.

What Is the DNS_PROBE_STARTED Error?

DNS (Domain Name System) is like the internet’s phonebook. When you type a URL into your browser, DNS translates the domain name into an IP address that computers understand.

The DNS_PROBE_STARTED error occurs when the browser cannot initiate a proper DNS lookup. Essentially, your system tries to contact the DNS server but fails to start the process successfully. Unlike other DNS errors, this one usually signals a problem with the device, network configuration, or DNS server rather than the website itself.

Common Causes of DNS_PROBE_STARTED

Several factors can trigger this error:

Incorrect DNS Settings – Misconfigured DNS servers can prevent proper domain resolution.

Outdated Network Drivers – Old or corrupt drivers may interfere with DNS queries.

Browser Cache or Corruption – Cached data or temporary glitches can cause the error.

Firewall or Antivirus Restrictions – Overly strict security software may block DNS requests.

Router or Modem Issues – Sometimes the network hardware itself causes connectivity problems.

Understanding the cause helps you choose the right solution to fix the issue.

Step-by-Step Fixes for DNS_PROBE_STARTED

Here’s how to troubleshoot and resolve this error effectively.

1. Restart Your Browser and Device

Sometimes, the issue is temporary. Restart your browser or close all tabs and reopen them. If that doesn’t help, restart your computer. This simple step often clears minor glitches in the DNS process.

2. Clear Browser Cache

A corrupted cache can cause DNS errors. Clearing your browser cache can resolve this:

Google Chrome: Go to Settings > Privacy and Security > Clear Browsing Data.

Choose Cached images and files and Cookies, then click Clear Data.

Restart the browser and try accessing the website again.

3. Flush DNS Cache

Your operating system stores DNS records locally to speed up browsing. A corrupted cache can trigger the DNS_PROBE_STARTED error.

For Windows:

1. Press Win + R, type cmd, and press Enter.
   
   

Run:

ipconfig /flushdns

For macOS:

Open Terminal and type:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

For Linux (Ubuntu/Debian):

sudo systemd-resolve --flush-caches

After flushing, restart your browser and check the website.

4. Restart Your Router or Modem

Sometimes, your network hardware causes the DNS lookup failure. Unplug your router, wait for 30 seconds, and reconnect it. This can reset network connections and fix the DNS_PROBE_STARTED error.

5. Change Your DNS Server

If your ISP’s DNS server is slow or unreliable, switching to a public DNS can resolve the issue.

Recommended public DNS servers in 2025:

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

On Windows:

Go to Control Panel > Network and Internet > Network and Sharing Center.

Select your active connection > Properties.

Highlight Internet Protocol Version 4 (TCP/IPv4) > Properties.

Select “Use the following DNS server addresses” and enter the new DNS.

On macOS:

Go to System Settings > Network.

Select your active connection > Details.

Go to DNS and add new servers.

6. Disable VPN or Proxy

VPNs or proxies may interfere with DNS resolution. Temporarily disable them and check if the error persists. If this fixes the issue, ensure your VPN or proxy settings are configured correctly.

7. Temporarily Disable Firewall or Antivirus

Some security software can block DNS requests. Disable your firewall or antivirus temporarily and see if you can access websites. If the problem resolves, adjust your software settings to allow DNS queries.

8. Update Network Drivers

Outdated or corrupt network drivers may trigger DNS errors. To update drivers:

On Windows:

Press Win + X > Device Manager.

Expand Network adapters.

Right-click your adapter > Update driver.

On macOS and Linux, ensure your system is up to date via system updates.

9. Reset TCP/IP Settings

On Windows, resetting TCP/IP can fix network-related DNS issues:

Open Command Prompt as Administrator.

Run the following commands one by one:

netsh int ip reset

netsh winsock reset

ipconfig /release

ipconfig /renew

Restart your computer afterward.

10. Check the Website or Domain

If DNS_PROBE_STARTED occurs only for one website, the problem might be with that site. Use tools like Whois Lookup or DNS Checker to see if the domain is active and properly configured.

Preventing DNS_PROBE_STARTED in 2025

Use reliable DNS servers like Cloudflare or Google.

Keep your operating system, browser, and network drivers updated.

Regularly clear DNS and browser cache.

Monitor domains for proper DNS configuration.

Avoid overly restrictive firewall or VPN configurations.

Final Thoughts

The DNS_PROBE_STARTED error can be disruptive, but it’s one of the easiest DNS issues to fix. By following these steps—from clearing cache to changing DNS servers—you can quickly restore your browsing experience.

Understanding the underlying causes helps prevent future occurrences, ensuring smoother internet access in 2025 and beyond. Whether you’re a casual user or managing a professional network, these fixes will help you stay connected without interruptions.