As well-polished an experience a browsing experience Google’s Chrome is, just like everything tech, it runs into a few bugs and glitches every so often.
In this article, we’re looking at the DNS_Probe_Finished_Bad_Config error and how you can resolve it to get your browser running back up again.
Restart your router
Power cycling your network equipment is the fix to more issues than you can think. More often than not, connectivity issues can be caused by an underlying bug in your router and can be fixed by rebooting.
Reset your DNS settings
As you can probably guess by the error, there might be something wrong with your DNS settings. Here’s how you can reset them.
Step 1: Press Windows key + R and type in cmd and hit enter.
Step 2: Type in ipconfig /flushdns to reset DNS settings to default.
If the above command doesn’t help, try entering these commands in the Command Prompt one at a time.
netsh winsock reset netsh int ip reset
If you suspect an issue with your router’s DHCP assignment, use these commands to release your old IP and request a new one.
ipconfig /release ipconfig /renew
If this doesn’t work either, use the following commands to reset your network stack.
ipconfig/flushdns nbtstat -R nbtstat -RR netsh int ip reset C:\resetlog.txt netsh winsock reset
On a mac, head over to your terminal and type in sudo killall -HUP mDNSResponder. Type your password when prompted for it and try re-accessing the internet. This should fix the DNS_Probe_Finished_Bad_Config error.
Try another DNS
There are multiple free DNS providers using whom you can fix this issue. In this example, we’re going to use Google’s DNS.
Step 1: Press Windows key + I to open the Windows settings and click on Network & Internet.
Step 2: Click on Change adaptor options.
Step 3: Right-click on your active network (WiFi or LAN) and click Properties.
Step 4: Find Internet Protocol Version 4 in the list, click on it and then click Properties.
Step 5: Check the Use the following DNS server addresses radio button and type in 220.127.116.11 and 18.104.22.168 in the preferred and alternative DNS addresses, respectively.
Try disabling your Windows firewall
Sometimes the Windows Firewall can be more of a hindrance rather than a security measure. Try disabling your firewall to check if you can get the browser up and running by fixing the DNS_Probe_Finished_Bad_Config error.
Step 1: Press the Windows key and search for Windows Firewall. Click on Firewall & network protection.
Step 2: Click on Private network or whichever is your active firewall.
Step 3: Toggle the Microsoft Defender Firewall setting off.
Now restart your browser and try again.
Clear the Chrome DNS cache
At times, a buggy DNS cache can redirect your browser to the wrong site and hence cause this error. You can try clearing Chrome’s DNS cache to see if the issue gets resolved.
Step 1: Fire up Chrome and head over to chrome://net-internals/#dns.
Step 2: Click on the Clear host cache button to clear out your DNS cache.
Restart the browser and try to access the site you were having issues with again.
Try resetting the netsh Winsock
Here’s another way you can try fixing the DNS_Probe_Finished_Bad_Config error.
Step 1: Press Windows Key + X or right-click on the Start button and click on Command Prompt (admin).
Step 2: Type the following command and press enter.
netsh winsock reset
If nothing else works, you can try resetting Chrome to ensure there are no faulty settings in the browser that could be causing this issue.
Step 1: Head over to chrome://settings/reset. Click on Restore settings to their original defaults.
Step 2: Chrome will show you a warning prompt. Click on Reset Settings, and your browser will reset to default settings.
Also read: How to install Chrome in Ubuntu?
Someone who writes/edits/shoots/hosts all things tech and when he’s not, streams himself racing virtual cars. You can reach out to Yadullah at [email protected], or follow him on Instagram or Twitter.