People are currently reading this guide.
Want to fix DNS_PROBE_FINISHED_BAD_CONFIG Chrome error? Is this DNS_PROBE error blocking you from accessing internet? You have landed on the right page. We have the steps mentioned below to get rid of this DNS_PROBE_FINISHED_BAD_CONFIG code on Chrome browser.
The DNS_PROBE_FINISHED_BAD_CONFIG error appears in the Google Chrome browser when you have a problem with your Internet connection and there are several easy ways to resolve it. You can read this article if you are getting error DNS_PROBE_FINISHED_NO_INTERNET.
Open a command prompt as described in the previous solution.
When the command prompt opens, Enter this line and click Enter to execute it:
That's all, I hope that at least one of these eight alternatives will assist you to fix the DNS_PROBE_FINISHED_BAD_CONFIG error in Windows 10. You can read more here for more errors like this.
What is DNS_PROBE_FINISHED_BAD_CONFIG
The error is DNS_PROBE_FINISHED_BAD_CONFIG very unusual and this error can seen in all versions of Windows. It is not surprising to see this error also in Windows 10. Don't worry, this error is very easy to fix and now we will show you how to do it.The DNS_PROBE_FINISHED_BAD_CONFIG error appears in the Google Chrome browser when you have a problem with your Internet connection and there are several easy ways to resolve it. You can read this article if you are getting error DNS_PROBE_FINISHED_NO_INTERNET.
Root Cause of DNS_PROBE Error
The error DNS_PROBE_FINISHED_BAD_CONFIG also known as DNS network service error. Usually, As we know that errors occur whenever user try to visit websites and surf the internet.
Some people claim that the DNS_PROBE_FINISHED_BAD_CONFIG error only affects Google Chrome, which is absolutely wrong. Because the problem does not directly affect the browser, Internet Explorer, Mozilla Firefox and Edge can also be affected.
This error is caused by network problems, incorrect configuration settings, inaccessibility of DNS servers or firewalls. Therefore, if the DNS server cannot translate an external server name due to a damaged configuration or for other reasons, a DNS_PROBE_FINISHED_BAD_CONFIG error stop giving access to many websites. Let me suggest you to read a fix for ERR_CONNECTION_REFUSED Error On Google Chrome
Even though it sounds complicated, you don't have to understand all the DNS specifications to correct the DNS_PROBE_FINISHED_BAD_CONFIG error.
All you have to do is follow the instructions provided below. Most users have overcome this problem themselves, so don't wait anymore.
All you have to do is follow the instructions provided below. Most users have overcome this problem themselves, so don't wait anymore.
How to Fix DNS_PROBE_FINISHED_BAD_CONFIG
There are certain ways in order to get rid of this chrome issue DNS_PROBE_FINISHED_BAD_CONFIG. Try and perform below steps one by one.Step 1: Renovate the IP address
But if a simple restart doesn't solve the problem with the DNS_PROBE_FINISHED_BAD_CONFIG error, you can try updating your IP address. And if you don't know how to do it, Just observe the following directions:- Use the Windows key + R and type cmd to run the command prompt.
- When the command prompt starts, type the following line and press Enter to run it:
- ipconfig /release
- This will free up your IP address.
- Now, enter this line and press Enter to run it:
- ipconfig /renew
Step 2: Flush the DNS cache
Then we will try to clear the DNS cache. To do this, follow these instructions:Open a command prompt as described in the previous solution.
When the command prompt opens, Enter this line and click Enter to execute it:
- ipconfig /flushdns
Step 3: Reset IP catalog
- Open Command Prompt and execute this line:
- netsh int ip reset
- Type this command and press Enter to execute it:
- netsh winsock reset catalog
Suggested: Seeing Code DNS_PROBE_FINISHED_NXDOMAIN on Chrome frequently?
Step 4: Change the DNS servers
And if none of the above helps, you can try changing the DNS server and see if the error has been resolved. To change the DNS server, follow these steps:- Press the Windows key + R and when the Run dialog box opens, type ncpa.cpl and press Enter.
- This will open the Network Connections window.
- Find your connection and right-click. Select one property
- Select Version 4 of the Internet Protocol and click Properties.
- Click Use the following DNS server address key in the Internet Protocol Version 4 Properties window.
- Set these values:
- Preferred DNS server: 8.8.8.8
- Alternate DNS Server: 8.8.4.4
- Click OK to save your settings.
Disable your Antivirus
If nothing works, Try to disable your antivirus. If you use Windows Defender,These are the steps to disable it:- Open Start, type "Windows Defender" in Cortana Search box.
- Click the first result to initiate the Windows Defender Security Center.
- Now click Virus Settings and Threat Protection.
- Access protection in real time and disable this option.
- After disabling your antivirus, Do the same for your firewall.
- Go to Start > Control Panel > System and Security > Windows Firewall
- Click the "Activate and deactivate Windows Firewall" option
- Turn off the firewall.
Reinstall or Update to Latest Network Drivers
If your network drivers are corrupted or outdated, this may explain why you’re getting the DNS_PROBE_FINISHED_BAD_CONFIG error. Go to Device Manager, and Update your network drivers and verify if this option works for you.Disable website blocking software
If you use a website blocker, temporarily disable this tool to see if this solution solves the problem. Some users have verified that the error vanished after the website blocker was disabled. Try this alternative to see if it works for you as well.Restart your router
It's very easy, Simply press the power button on the modem, wait a moment and restore your router. This will reset your IP address and correct the problem.That's all, I hope that at least one of these eight alternatives will assist you to fix the DNS_PROBE_FINISHED_BAD_CONFIG error in Windows 10. You can read more here for more errors like this.