How to Fix the Chrome Error: DNS_PROBE_FINISHED_BAD_CONFIG on Windows 11

If you are using Google Chrome and are getting The DNS_PROBE_FINISHED_BAD_CONFIG error that prevents websites from loading. There's a solid chance you have some Internet and network issues that need to be fixed. Thankfully, there are quite a few quick and easy steps you can take to solve this issue. There's a good chance that you're probably familiar with some of them as well.

How to Fix the Chrome Error: DNS_PROBE_FINISHED_BAD_CONFIG on Windows 11

Before you even consider doing anything else in this guide, make sure you have done the following things first. There's a 99% chance they will solve the problem.

Flush the DNS Cache, Reset TCP/IP and Winsock

These commands clear and reset DNS and networking configurations.

Enter the following commands one by one, pressing Enter after each:

ipconfig /flushdns

ipconfig /registerdns

ipconfig /release

ipconfig /renew

netsh winsock reset

Change DNS Server to Google DNS

Switching to a public DNS like Google’s can help bypass provider-specific issues.

Windows 11:

Preferred DNS: 8.8.8.8
Alternate DNS: 8.8.4.4

Windows 10:

Preferred DNS: 8.8.8.8
Alternate DNS: 8.8.4.4

Temporarily Disable Antivirus and Firewall

Security software may block DNS traffic.

Update Network Drivers

Outdated drivers can cause DNS resolution problems.

Reset Chrome Settings

Misconfigured browser settings can also cause DNS issues.

Comments