Resolving the DNS_PROBE_STARTED Error

It is common to encounter issues while navigating the web or loading web pages. One of the frequent obstacles that users face is the DNS_PROBE_STARTED error, which is linked to the Domain Name Server (DNS) system.

This error can disrupt your online activities but can be managed through several simple and effective strategies to restore seamless internet access.

In this article, we will explore the essence of the DNS_PROBE_STARTED error, its usual triggers, and six practical methods for rectifying it. Let’s get started!

Overview

• Understanding the DNS_PROBE_STARTED Error
• Primary Reasons Behind the DNS_PROBE_STARTED Alert
• Step-by-Step Solutions to Overcome the DNS_PROBE_STARTED Error

Deciphering the DNS_PROBE_STARTED error

This error message usually appears when your device is having trouble connecting to a DNS server. It means a DNS probe diagnostic test has encountered issues while checking the device’s DNS connectivity.

DNS, which tracks domain names and their IP addresses, translates easy-to-remember domain names into numerical IP addresses. This allows us to access websites without having to remember their IP addresses.

A DNS probe is a diagnostic test that checks whether a website or IP address is accessible and whether the DNS servers work efficiently. There are various DNS-related errors, such as:

• DNS_PROBE_BAD_CONFIG
• DNS_PROBE_FINISHED_NXDOMAIN
• DNS SERVER NOT RESPONDING

DNS_PROBE_STARTED indicates explicitly that the diagnostic process has failed to initiate.

This issue is common in web browsers like Chrome but can occur on different platforms.

Common causes of the DNS_PROBE_STARTED error

If you see an error message that says “DNS_PROBE_STARTED, ” it means that your device is unable to connect to the DNS server. This can happen due to incorrect network or DNS settings, issues with network adapters or routers, or interference from antivirus or firewall applications.

Solutions for the DNS_PROBE_STARTED error

To fix this error, you must troubleshoot your browser, network, and device. The specific steps to follow may vary depending on the type of operating system and device you are using. However, the solutions provided apply to many operating systems, browsers, and platforms.

1. Start by switching to alternative DNS servers for potential resolution.
2. Clearing your DNS cache can eliminate outdated or incorrect DNS information, potentially solving connectivity issues.
3. Clearing your browser’s cache and cookies might address the error by eliminating stored data that could be causing conflicts.
4. Outdated or faulty network drivers could be to blame. Uninstalling and reinstalling them might rectify the problem.
5. Sometimes, antivirus or firewall settings may inadvertently block DNS requests. Adjusting or temporarily disabling these can help identify if they’re the cause.
6. In some cases, restarting your networking devices can refresh your connection to DNS servers and resolve the error.

Step-by-step instructions

1. Change your DNS server address

Changing your IPv4 or IPv6 DNS addresses can help bypass network congestion or issues with your current DNS server, potentially resolving the DNS_PROBE_STARTED error. Here’s how to do it:

For Windows:

1. Open Control Panel and navigate to “Network and Internet”> “Network and Sharing Center”.
2. Click on “Change adapter settings” on the left menu.
   
3. Right-click your active network connection (Wi-Fi or Ethernet) and select “Properties”.
4. Scroll down and select “Internet Protocol Version 4 (TCP/IPv4)” or “Internet Protocol Version 6 (TCP/IPv6)” and click “Properties”.
5. Select “Use the following DNS server addresses” and enter the new DNS server addresses (e.g., Google DNS: 8.8.8.8 for Preferred and 8.8.4.4 for Alternate).
   
   
6. Click “OK” to save your changes and close all windows.

For macOS:

1. Go to System Preferences > Network.
2. Select your active connection and click “Advanced”.
3. Switch to the DNS tab.
4. Click the “+” button to add new DNS servers and enter the DNS addresses.
   
   
5. Click “OK”, then “Apply” to save the changes.

2. Refresh Your DNS

Flushing your DNS cache removes outdated entries and can solve DNS-related errors by forcing your computer to update its DNS records.

Windows:

1. Press Windows key + R, type “cmd”, and press Enter.
2. Type `ipconfig /flushdns` and press Enter.
3. Optional: Renew IP and re-register DNS with `ipconfig /renew` and `ipconfig /registerdns`.

macOS:

1. Open Terminal.
2. Type `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder` and press Enter. Enter your password if prompted.
   
   

3. Clear your browser cache and cookies

An outdated cache and cookies can cause DNS errors. Clearing them might resolve the issue.

Clearing cache and cookies on Chrome:

1. Click the three dots in the upper right corner of Chrome to open the menu. Select “Settings.”
2. Scroll down and click on “Privacy and security.”
   
3. Click on “Clear browsing data.”
4. In the “Basic” tab, check the boxes for “Cookies and other site data” and “Cached images and files.” You can also select the time range; to clear everything, select “All time.”
   
   
5. Click the “Clear data” button to remove your selected browsing data.

For all browsers:

Access your browser’s settings to find the option to clear browsing data. Ensure that you select the option to clear cache and cookies and set the time range to “All time” or the maximum available option.

4. Uninstall and reinstall your network driver(s)

Outdated or corrupted network drivers could be the cause of DNS issues.

Windows:

1. Press Windows key + R, type “devmgmt.msc”, and press Enter to open Device Manager.
   
2. Expand “Network adapters,” right-click your network device, and select “Uninstall device.”
3. Restart your PC. Windows will attempt to reinstall the network driver automatically.

macOS:

Network drivers are generally managed automatically by macOS, but ensuring your system is up to date can prevent or resolve issues.

5. Disable antivirus and firewall temporarily

Sometimes, security software might mistakenly block DNS requests.

Check your antivirus and firewall settings to ensure they’re not interfering with your network connections. Consider temporarily disabling them to test if this resolves the issue.

Remember to re-enable them afterward for your protection.

Disable Windows firewall:

1. Press the Windows key, type “Control Panel,” and press Enter.
2. Click on “System and Security,” then click on “Windows Defender Firewall.”
   
   
3. On the left side, click “Turn Windows Defender Firewall on or off.”
4. Under both “Private network settings” and “Public network settings,” select the “Turn off Windows Defender Firewall (not recommended)” option.
5. Click “OK” to save your changes.

Disable antivirus protection in Windows:

The steps to disable antivirus software can vary depending on the antivirus program installed. Here’s a general guide:

1. Click the upward arrow on the taskbar to open the system tray.
2. Locate your antivirus icon; it may be Norton, McAfee, AVG, etc.
3. Right-click on it and look for an option like “Disable,” “Stop,” “Turn Off,” or something similar. Sometimes, you might have to open the antivirus application and disable it from within the settings.

Disabling firewall on a Mac:

1. Click on the Apple menu and select “System Preferences.”
2. Click on “Security & Privacy.”
3. Go to the “Firewall” tab.
4. To make changes, click the lock icon in the bottom left corner (you may need to enter your admin password).
5. Click “Turn Off Firewall” to disable the firewall.
   
   
6. Click the lock icon again to prevent further changes.

6. Restart your router/modem

A simple restart can resolve network connectivity issues by clearing any temporary glitches in the hardware.

Unplug your router and modem from their power sources, wait a minute, and plug them back in. Wait for all the lights to stabilize before testing your connection. It can also help to restart your device at this point.

Conclusion

Resolving the DNS_PROBE_STARTED error often involves a process of elimination, from refreshing your DNS settings to checking for broader network hardware issues. By following these detailed steps, you should be able to diagnose and fix the problem, restoring your access to the internet and specific websites without encountering this pesky error.

Still having trouble? Share your questions in the comments!