How to Fix DNS_PROBE_FINISHED_BAD_CONFIG Error in Chrome: 11 Ways

When you access a website, many elements work together to load it. If there is a problem with your DNS settings, Internet connection, files or third-party applications, it is likely that an error will occur.

Whether you’re a website owner or a visitor, running into a problem can be irritating as it could prevent you from viewing the site. If you use Google Chrome, DNS_PROBE_FINISHED_BAD_CONFIG is one of the errors you may encounter.

In this article, we will discuss what DNS_PROBE_FINISHED_BAD_CONFIG error is and go through 11 ways to fix it.

Error codeDNS_PROBE_FINISHED_BAD_CONFIGbug typeNetwork connection errorbug variationsThis site cannot be accessedThis web page is not availableSafari cannot find the serverCauses of the errorMisconfiguration in Network and DNS Settings Third Party Apps/Extensions Corrupt Files Browser Cache DNS Cache

doWhat is ERROR DNS_PROBE_FINISHED_BAD_CONFIG?

DNS_PROBE_FINISHED_BAD_CONFIG indicates a network connection problem that occurs when DNS cannot find the web server associated with a domain name or IP address. As a result, the website is inaccessible and visitors get an error message like “This site cannot be accessed”.

11 Solutions to Fix DNS_PROBE_FINISHED_BAD_CONFIG Error in Chrome

Before you begin, it is important to understand . It directs Internet traffic and connects web servers with nameservers, URLs, and IP addresses.

Visitors to a website simply type a domain name into their browser, and the DNS server will look up the URL and connect it to the appropriate web server. If the process cannot be completed successfully, an error such as DNS_PROBE_FINISHED_BAD_CONFIG may appear.

Indicates that there is something wrong with your DNS settings, network connection, or third-party applications, preventing visitors from reaching the website. In this section, we will go through 11 solutions to fix DNS_PROBE_FINISHED_BAD_CONFIG error.

1. Reboot the router

You may encounter a number of Internet connection problems when browsing websites. Sometimes web pages may take a long time to process your requests or may not load at all.

If you encounter the DNS_PROBE_FINISHED_BAD_CONFIG error, start troubleshooting by checking your router. Turn it off and wait about a minute before turning it back on. Alternatively, unplug the internet cable and wait another minute before plugging it back in.

Restarting the router will reestablish the connection with the Internet service provider. In most cases, this will be enough to resolve the DNS_PROBE_FINISHED_BAD_CONFIG error.

2. Reboot the device

If your computer has been on for a long time, you may encounter software, memory, and even network connection problems. Reboot your device regularly to maintain its health and prevent slowdowns.

Once the device turns on again, it will reconnect to the Internet. This may resolve DNS errors, try it after rebooting your router for best results.

3. Clear browser cache

Browsers cache information so they can load a site much faster the next time you visit it. The more sites you access, the more data the browser will cache, increasing the chances that it will become corrupted and may cause DNS errors.

completely is an effective way to resolve the DNS_PROBE_FINISHED_BAD_CONFIG error. All browsers have this feature – here are the steps to do it in Google Chrome:

Click on the three point menu in the upper right corner of your browser.
Mouse over More tools and select Clear browsing data.
Choose a Weather and click Delete data.

4. Disable antivirus and firewall

Antivirus software and firewall provide protection against malware. That said, it can interfere with your network connection and even DNS settings, blocking access to some web pages.

Try temporarily disabling your firewall and antivirus software to see if that fixes the DNS_PROBE_FINISHED_BAD_CONFIG error. The methods may vary depending on the operating system and antivirus software you use.

On Windows, you can disable protection through the app windows security.

Write windows security in the search field on the taskbar and tap enter.
Choose the configuration of the virus and threat protection.
Change the Real-time protection a disabled.

To disable Windows Firewall, go to Firewall and network protectionChoose one private network either public and change the Microsoft Defender Firewall a disabled.

Keep in mind that your computer may be exposed to malware if you disable antivirus and firewall protection permanently. If you’ve determined that antivirus software was the cause of the error, try contacting support for help.

5. Disable website blockers

Website blocker extensions can cause DNS_PROBE_FINISHED_BAD_CONFIG errors. This is because they interfere with your network settings to prevent ads and websites from redirecting you without your consent.

The best way to solve the problem is to disable the website blocker extensions or remove them from the browser altogether.

Here’s how to disable website blockers in Google Chrome:

Open the three point menu
Mouse over More tools and click Extensions.
Disable the website blocker extension.

To remove the extension, click Put off.

6. Delete temporary files

Browsers and operating systems save temporary Internet files, such as cached websites, cookies, and browsing history details. There is a high probability that they will become corrupted, leading to the DNS_PROBE_FINISHED_BAD_CONFIG error.

One of the solutions is to delete the temporary files. Here’s how to do it on Windows:

enter %temp% in the search field on the taskbar.
The temporary directory will open.

Select all the files and folders and delete them.

If this doesn’t resolve the DNS_PROBE_FINISHED_BAD_CONFIG error, continue to the next step.

7. Flush DNS

The DNS cache keeps records of IP addresses every time you visit a website. If you change any DNS settings, this information will be updated, allowing the DNS server to point you to the correct IP address when trying to access a site.

However, if your system relies on data from the local cache when connecting to the network, you may encounter the DNS_PROBE_FINISHED_BAD_CONFIG error. To fix it, you’ll have to .

To flush the DNS cache on Windows, follow these steps:

Write cmd in the search field on the taskbar.
Right-click on the icon of the Symbol of the system and select Execute as an administrator.
Write ipconfig /flushdns in the window of symbol of the system and press enter.

8. Change DNS settings

Internet service providers distribute DNS server addresses by default. However, in some cases, the servers may experience problems, affecting your connectivity.

Try changing your system’s DNS server address to fix the DNS_PROBE_FINISHED_BAD_CONFIG error. We recommend that you use a public DNS server such as the one provided by Google.

Here’s how to change DNS server addresses in Windows:

Open the menu Start and select Setting.
Choose Network and Internet.
click on Properties and select Edit.

Choose Manual and activate the option IPv4. inside the field preferred DNS, enter the IP address 8.8.8.8. Enter in alternate DNS 8.8.4.4. Click Save to confirm the changes.

Follow these instructions to change DNS server addresses on macOS:

Open the menu of Manzana and select System preferences.
click on Net and select your Internet connection in the left panel.

click on Advanced…
Switch to tab . With sign icon plus that appears below the field DNS serversadd the IP addresses 8.8.8.8 and 8.8.4.4.
click on To accept and in Apply to save the changes.

Changing the DNS server addresses should resolve the DNS_PROBE_FINISHED_BAD_CONFIG error in most cases.

9. Reset network settings

If the above methods didn’t work, try resetting your network settings. This will restore the original values and establish a new connection.

To reset network settings in Windows, follow these steps:

Open the menu of Start and choose Setting.
click on Network and Internet and select Advanced network settings.
Choose Network reset.

click on reset now.

Here’s how to do it on macOS:

Open the launch pad and writes Terminal. Run the app.
Write cd/Library/Preferences/System Configuration/ and press Return to change the active directory.

run the command rm -f preferences.plist NetworkInterfaces.plist com.apple.airport.preferences.plist com.apple.wifi.message-tracer.plistthis will remove the network configuration files.
Write sudo killall -HUP mDNSResponder ; sudo dscacheutil -flushcache to flush the DNS cache.

10. Renew IP address

Renewing your IP address is another way to fix the DNS_PROBE_FINISHED_BAD_CONFIG error. Your computer will request a new IP address from the Dynamic Host Configuration Protocol (DHCP) server or router. Before renewal, please make sure to release the old IP address first.

Here’s how to do it on Windows:

Write cmd in the search field on the taskbar.
Right click on Symbol of the system and choose Execute as an administrator.
Run the following commands:

ipconfig /release

ipconfig /renew

11. Update network driver

Outdated network drivers can cause a number of issues, including the DNS_PROBE_FINISHED_BAD_CONFIG error. Therefore, it is important to check if your network drivers are up to date.

To update network drivers in Windows, follow these steps:

Write Device administrator in the search field on the taskbar and tap enter.
Choose Network adapters.
Update the drivers for each network adapter by right-clicking on one of them and selecting Update driver.

Restart your device and try to access the web page again.

If you are a Mac user, you don’t have to worry about network drivers as long as you update the operating system. Here we explain how…