dns_probe_finished_bad_config Frequently, But No Network Disconnection

My Lenovo C940 laptop has an Intel Wireless-AC 9560 160MHz network adapter. Windows 10 Home 1909.

Using either up-to-date Chrome or the latest version of Microsoft Edge.

Frequently, when I navigate to most new sites (I won't list every site, but they're highly varied -- not just google news, google calendar, gmail, etc.) I first get the dns_probe_finished_bad_config error. It appears for a couple seconds then the site loads automatically or once I click Refresh, it loads.

This issue can happen repeatedly, where this problem occurs for every site I access; or they can disappear and not occur at all for minutes or hours at a time.

The network never disconnects. I can also be streaming, or in a webinar, or any other downloading/uploading activity might be happening, and they continue uninterrupted, at normal high speeds.

What is going on here? How can I begin to troubleshoot it? The problem description is not easy to google :P

Try setting your DNS to a fast 1.1.1.1 & 1.0.0.1

Samuria said:

Try setting your DNS to a fast 1.1.1.1 & 1.0.0.1

Trying this now. First couple minutes are good, but as the original post notes, will need to give it an hour of trialling. If it works, I'll be REALLY curious to know the mechanics of why it works... I only have this problem on my laptop. Up to 8 different devices on the same network do not face this problem.

Paul Black said:

Hello @mike302,



Actually, I have just Googled this an found this which you might find interesting . . .

Introducing DNS Resolver, 1.1.1.1 (not a joke)

I hope this helps!

Thanks, that's an interesting read. I suppose I should reword my last post though -- why has this come about all of a sudden? 2-3 days ago, I didn't have this problem so much. A week ago, it definitely wasn't a problem. There seems to be an increasing need to set this DNS setting. Why has that happened? Also, I stand corrected -- one other user on the network has noticed similar browsing symptoms, so maybe it's to do with the ISP... Plusnet, UK.

- - - Updated - - -

Samuria said:

Try setting your DNS to a fast 1.1.1.1 & 1.0.0.1

So this solved it. I'm not an internet architect guru, so I'm curious why something so simple fixed this, and why this problem cropped up for a few computers on my household wifi in the past week -- in the simplest terms possible I guess :P