In reply to a post by j0hn83:

Not as old as 19628 but it's a 21H1 insider release 🤦🏻‍♂️

I would urge caution then, since Win10 builds 19044 and 19045 are the only ones receiving security updates. 19045 is the final build before retirement.

In reply to a post by jchamier:

9.9.9.9 for Quad 9
https://www.quad9.net/

Or 1.1.1.1 for Cloudflare
https://1.1.1.1/dns/

I avoid google (8.8.8.8) for privacy reasons.

very wise move imo

I was using Cloudflare 1.1.1.1 and 1.0.0.1 until yesterday, when Cloudflare started dropping.
I was getting about 3% packet loss initially, but it's now up to 14%.

I switched to a hyprid Quad9 9.9.9.9 as primary with Cloudflare 1.0.0.1 as secondary.

In reply to a post by RogueAlice:

I switched to a hyprid Quad9 9.9.9.9 as primary with Cloudflare 1.0.0.1 as secondary.

I'm interested to know why you went for 1.0.0.1 for your secondary and not 1.0.0.2 or 1.1.1.2 as I thought that was the Cloudflare equivalent of 9.9.9.9

In reply to a post by RogueAlice:

I switched to a hyprid Quad9 9.9.9.9 as primary with Cloudflare 1.0.0.1 as secondary.

Secondary servers are only used if the first does not respond at all.

In reply to a post by jchamier:

Secondary servers are only used if the first does not respond at all.

Not in my experience. I just packet monitored port 53 while firing some dns queries off via ping requests, and the lookups were spread evenly across both servers defined in Windows.

In reply to a post by Oliver341:

In reply to a post by jchamier:

Secondary servers are only used if the first does not respond at all.

Not in my experience. I just packet monitored port 53 while firing some dns queries off via ping requests, and the lookups were spread evenly across both servers defined in Windows.

A few routers I've checked in the past load balanced across all DNS servers but I can't say that's always the behaviour of all routers/devices.

there is also https://dns.watch for anyone interested (not very fast I think)

In reply to a post by Oliver341:

Not in my experience. I just packet monitored port 53 while firing some dns queries off via ping requests, and the lookups were spread evenly across both servers defined in Windows.

That's interesting.... I wonder if MS has changed behaviour in a recent IP stack.

In reply to a post by jchamier:

That's interesting.... I wonder if MS has changed behaviour in a recent IP stack.

Certainly possible, I couldn't find any official docs on what the behaviour is meant to be.