The DNS_PROBE_FINISHED_BAD_CONFIG error is a common networking issue that occurs when your browser cannot resolve a domain name due to a misconfiguration in your DNS settings or network stack. This error can strike on Windows, macOS, or Android, effectively cutting off your access to the internet even if your hardware is working perfectly.

In this guide, we will walk through the most effective technical solutions to resolve this error and get your connection back online.

1. Restart Your Router and Computer

Before diving into complex settings, start with a power cycle. DNS errors are often caused by temporary glitches in the router's cache or the local device's network state.

• Unplug your router from the power source and wait for at least 30 seconds.
• Plug it back in and wait for the lights to stabilize.
• Restart your computer to clear out temporary system memory related to network processes.

2. Flush the DNS Cache and Reset Winsock

Windows stores a database of IP addresses in a local cache to speed up loading times. If this cache becomes corrupted, it leads to the "BAD_CONFIG" error. Using the Command Prompt as an Administrator is the fastest way to fix this.

• Type cmd in the Windows search bar, right-click it, and select Run as Administrator.
• Type the following command and press Enter: ipconfig /flushdns
• Next, type: ipconfig /release and press Enter.
• Then, type: ipconfig /renew and press Enter.
• Finally, reset the network catalog by typing: netsh winsock reset and press Enter.
• Restart your PC to apply these changes.

3. Change Your DNS Servers Manually

By default, your computer uses the DNS servers provided by your ISP. If these servers are down or poorly configured, you will see the DNS_PROBE_FINISHED_BAD_CONFIG error. Switching to Google Public DNS or Cloudflare often resolves the issue.

• Press Windows + R, type ncpa.cpl, and hit Enter.
• Right-click your active connection (Wi-Fi or Ethernet) and select Properties.
• Highlight Internet Protocol Version 4 (TCP/IPv4) and click Properties.
• Select Use the following DNS server addresses.
• Set Preferred DNS server to 8.8.8.8 and Alternate DNS server to 8.8.4.4 (Google) or use 1.1.1.1 and 1.0.0.1 (Cloudflare).
• Check Validate settings upon exit and click OK.

4. Disable Temporary Files and Browser Cache

Sometimes the error isn't in your system settings but within the browser itself. Corrupted "Bad Config" data can be cached locally.

• Open your browser (Chrome, Edge, or Firefox).
• Press Ctrl + Shift + Delete to open the Clear Browsing Data menu.
• Select Cached images and files and Cookies and other site data.
• Set the time range to All time and click Clear data.

5. Update Your Network Adapter Drivers

Outdated or incompatible network drivers can cause communication breakdowns between your OS and the DNS protocol.

• Right-click the Start button and select Device Manager.
• Expand the Network adapters section.
• Right-click your primary network controller (e.g., Intel Wi-Fi or Realtek Ethernet) and select Update driver.
• Choose Search automatically for drivers and follow the prompts to install any updates.

6. Disable Antivirus and Firewall Temporarily

Occasionally, over-aggressive security software identifies valid DNS requests as suspicious activity and blocks them. To test this, temporarily disable your third-party antivirus or the Windows Defender Firewall. If the website loads immediately, you will need to whitelist your browser or reset your firewall rules to their default settings.

💡 Pro Tip: Keep your software updated to avoid these issues in the future.