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

Key Takeaways

• DNS_PROBE_STARTED errors occur when the browser fails to start the DNS search process.
• Common causes include network issues, DNS problems, or device settings.
• Simple and advanced fixes are covered in the guide, suitable for all tech skill levels.
• Managed hosting platforms like Cloudways offer built-in DNS support to help prevent such errors.

You’re browsing the web, checking an email, or reading a page when suddenly the site won’t load. Instead, you’re greeted with the error: DNS_PROBE_STARTED. It’s frustrating, but what does it actually mean, and why does it stop you from accessing the website?

The error happens when your browser attempts to look up a website’s DNS but fails to complete the process. It’s like asking for directions, only for your GPS to freeze before giving you any results.

In this guide, we’ll explain the root cause of the issue and walk you through how to fix it. And if you’re using a managed hosting platform like Cloudways, their built-in DNS tools can help prevent these errors from happening in the first place.

Now, let’s dive into the details of what DNS is and why it’s so important for your browser’s functionality.

What Is the DNS_PROBE_STARTED Error?

The DNS_PROBE_STARTED error occurs when your browser attempts to look up a website’s DNS but fails to complete the process.

It essentially means that the connection between your browser and the website couldn’t be established due to DNS-related issues.

To understand it in detail, let’s quickly dive into what DNS is and why your browser depends on it.

Understanding DNS and Why It Matters

You may think of DNS (Domain Name System) as a phone book for the internet.

When you type a website address like example.com, DNS helps your browser find the corresponding IP address so it can connect to the right server. Without a working DNS, your browser can’t find the site, which is when errors like DNS_PROBE_STARTED appear.

What Does “PROBE_STARTED” Actually Mean?

“PROBE_STARTED” indicates that your browser initiated the DNS query, but something caused it to fail before completion.

This could happen due to a variety of reasons, such as a local issue on your device, a misconfigured network, or external factors blocking the request.

How This Error Appears in Different Browsers (Chrome, Firefox, Edge)

The way this error shows up can vary depending on the browser you’re using:

• Chrome: “This website cannot be achieved – DNS_PROBE_Started“.
• Firefox: It can display a “server that is not observed” with hints of DNS failure.
• Edge: It usually shows “hmmm… cannot reach this website” that could include DNS indicators under diagnostics.

What Causes the DNS_PROBE_STARTED Error?

Let us see some common reasons for this error. It allows you to know if there is a problem for your system, your browser, your community or maybe it is something not concerning your server.

DNS Server Failures or Misconfigurations

Sometimes the DNS servers your system is using are down or incorrectly configured. In such cases, DNS queries never get answered.

Network Adapter or Router Issues

A failing router or outdated network adapter driver might block or drop DNS requests without warning.

Antivirus or Firewall Interference

Security tools are great until they get in the way. Overzealous firewalls or antivirus software can interfere with DNS communication.

Corrupt Browser Cache or Cookies

Your browser saves temporary data to improve speed. But if those records are corrupt or stale, DNS requests may behave unpredictably.

Fast Startup Feature (Windows-specific)

Windows Fast Startup saves system states to boot quicker, but it may also retain faulty network configurations from a previous session.

OS-Level Configuration or Driver Conflicts

Drivers and system settings can go out of sync. When they do, DNS operations might not even start, causing this error.

Go live online sooner with Cloudways DNS Made Simple.

Easily manage your domains and stay in full control of your website’s presence.

TRY NOW

Quick Checks Before You Troubleshoot

Before we get into the fixes, it’s highly recommended to try these quick checks first, they’re often all you need.

1. Test Site on Another Browser or Device

Open the same website on your phone or a different browser. If it works there, your issue is likely browser- or device-specific.

2. Use Incognito Mode to Rule Out Cache

Open an Incognito window. If the site loads, your regular browser cache or extensions are likely at fault.

3. Check DNS Status Using Online Tools

Visit a DNS propagation checker like dnschecker.org. Type in the domain and see how it resolves globally. If most checks fail, the issue might not be on your end.

How to Fix the DNS_PROBE_STARTED Error (Windows/MacOS/Linux)

To fix the DNS_PROBE_STARTED error, immediately clear your browser’s DNS cache by navigating to chrome://net-internals/#dns and clicking “Clear host cache”. If the error persists, flush your DNS via Command Prompt (Windows: ipconfig /flushdns; Mac: dscacheutil -flushcache), change your DNS servers to Google DNS (8.8.8.8 / 8.8.4.4) or Cloudflare DNS (1.1.1.1), and restart your router.

Here’s a step-by-step guide to the most reliable fixes, explained in simple terms so you can follow along, even if you’re not very tech-savvy.

1. Change Your DNS Server

If your DNS provider is slow or down, using Google (8.8.8.8) or Cloudflare (1.1.1.1) can improve reliability.

For Windows:

• Go to Control Panel → Network and Sharing Center

• Click Change adapter settings.

• Right-click your connection → Properties

• Select Internet Protocol Version 4 (TCP/IPv4) → Properties
• Select “Use the following DNS server addresses” Enter your DNS

macOS/Linux:

• Update DNS settings under System Preferences → Network or edit /etc/resolv.conf.

2. Flushing DNS and IP recovery

Flushing clears old DNS entries, renewing resets your connection. Sometimes your machine holds old or damaged DNS items. Let’s clean them using the following commands.

For Windows command line:

IPCONFIG /FLUSHDNS
IPCONFIG /Start
Ipconfig /renew

For MacOS terminal:

DSCACHEUTIL -FLUSHCACHE
SUDO KILLALL -HUP MDNSRESPONDER

3. Clear Cache and Cookies

In order to clear the cache and cookies from your browser, follow the steps below:

• Go to your browser’s settings → Delete viewing information
• Select cache and cookies
• Delete them

Then you need to restart the browser and it’s done. If your browser has old web data or redirect data, it will block the radiant name DNS so this step will help.

4. Temporarily Deactivate Antivirus or Firewall

The security software or your antivirus software can block DNS. Now in order to check this, you need to temporarily deactivate antivirus or firewall.

If the error disappears, it means the firewall is likely causing the issue. You can then adjust the firewall settings as needed.

5. Reboot the Router and Modem

Rebooting the router or your modem can help with such error glitches. You can disconnect your device for about 30 seconds and connect it again to test.

Doing so clears the cache settings, resets the connection, and helps fix intermittent issues.

6. Reinstall or Update Your Network Drivers

You can also try re-installing or updating your network driver settings in order to deal with these errors. You can follow the following steps.

For Windows:

• Open “Device Manager” → “Network Adapters”.
• Right click on “adapter” → “Update theme strength” or “Uninstall”.
• Then restart your system in order to apply changes.

On MacOS/Linux:

• Using System or CLI updates to reinstall network components.

7. Disable Quick Startup (Windows Only)

• You need to open “Control Panel” → “Power Options”.

• Next click “Choose what the power buttons do”.
• Then click “Change settings that are currently unavailable”.

• Next you need to uncheck “Turn on fast startup”. And that’s it.

Bonus Fixes That Might Work (Advanced Users)

If you want to try some advanced fixes, here are few bonus tips in order to deal with these errors.

Use a Static IP Instead of DHCP

Dynamic IP addresses can sometimes cause DNS hiccups. Assigning a static IP gives you better control. Here are the steps to follow:

For Windows:

• Go to Network Settings → Adapter Options → IPv4
• Choose “Use the following IP address” and set values manually

Use the DNS Chrome internal page

• Enter chrome://net-internals/#dns in Chrome’s address bar
• Click Clear host cache

• Test the site again

This can be particularly advantageous if Chrome puts on terrible DNS statistics.

When to Contact Your Hosting Provider or ISP

If none of the above steps fix this problem, it may be your hosting provider issue.

Signs It’s Not a Local Problem

• Error indicates on all devices in your network.
• DNS Gear Show Failed resolution from external servers.
• Ping/traceroute fails beyond your local network.

What To Do Next

• Contact your ISP if multiple sites fail.
• Contact your web host (e.g., Cloudways) with DNS checker or traceroute results.

Avoid DNS Errors with Managed DNS Integration

If you own a website, you can avoid many DNS problems by selecting a web hosting provider that provides managed DNS and infrastructure.

Built-in DNS Monitoring and Propagation Alerts

Providers like Cloudways reveal DNS configurations and spread across areas. You will receive notifications if something is off, which helps you with problems with traps before visitors are affected.

Easy DNS Configuration via the Cloudways Platform

Cloudways offers an easy panel to replace your DNS information – if you won’t be able to manually set up the registrar. You can sign up for DNS made easy Addon to set up the DNS.

You can activate the desired plan as per your requirements. You will see the instructions and details on the add-on page.

You can add the domain along with the DNS details as per the instructions you will be getting on your Cloudways Platform screen.

How Cloudways Minimizes DNS-Related Errors

1. Automated SSL and DNS Renewal

Cloudways automatically installs and renews SSL certificates using Let’s Encrypt, so you don’t have to worry about certificates expiring and causing errors. It also keeps your DNS settings correctly managed to avoid issues.

2. Stable DNS Configuration

Cloudways ensures your DNS records (like A and CNAME) are properly set up and stable at the server level with DNS made easy add-on, helping your domain reliably point to your site with minimal downtime or errors.

3. Expert Integrated Support

Cloudways support team is familiar with DNS timing and SSL renewal schedules, helping you quickly fix any DNS or SSL problems related to propagation delays or configuration issues.

Final Thoughts

DNS errors such as `DNS_PROBE_Started` may look intimidating, but are generally fixed with some quick steps. If you have gone through this guide, you will now realize what triggers this error, a way to restore it in different systems and browsers, no matter if it’s for your IssP issuer or your web hosting end issue.

In addition, hosting your website on a managed hosting platform, such as Cloudways, makes it easier to avoid DNS errors thanks to integrated monitoring, computer updates and professional assistance. Hopefully, this guide has provided you with clarity and confidence in solving such error difficulties and may even save you from getting stuck with such errors again.