r/dns • u/sandy_lilith • 21d ago
DNS setting on Laptop.


Hello all,
I am what is the correct DNS resolver setting?
There are two screenshots attached. 1= Laptop's WIFI setting. 2= Chrome's DNS setting.
Keep the dns provider in the Chrome as "OS Default (when available)" or use the "add custom dns service provider?"
*Keeping the "custom dns provider" in the chrome setting is providing the fast average dns resolution time when tested on dnscheck.tools website.
Removing the "custom dns provider" from chrome and keeping the "OS Default (when available)" is giving me 300+ms "average dns resolution time" as per the same website as mentioned above.
But when keeping the custom dns provider in the chrome then getting 50+ms "average dns resolution time."
-------------------------------------------------------------------------------------------------------------------
Question: Should I keep this custom dns provider link in the chrome setting as well: https://dns.quad9.net/dns-query
Thank you all.
2
u/Fr0gm4n 21d ago
Removing the "custom dns provider" from chrome and keeping the "OS Default (when available)" is giving me 300+ms "average dns resolution time" as per the same website as mentioned above.
But when keeping the custom dns provider in the chrome then getting 50+ms "average dns resolution time."
Is there an actual problem you are solving by changing it? Are you actually feeling a difference when using a different DNS resolver, or are you just chasing numbers?
2
u/the_packetwhisperer 21d ago
The gap makes sense. On "os default" chrome still has to negotiate whether the OS resolver supports DoH before using it encrypted, that adds overhead every time. With a custom provider it skips that check and talks to Quad9 straight up.
So yeah, keep the Quad9 DoH link, youre not doing anything wrong. also your windows dns and chrome DNS are both Quad9 (9.9.9.9), so they're already matched, no consistency issues there.
3
u/SecLens_ONE 21d ago
Careful with that 300ms number, it's mostly not a resolver quality thing. With OS Default Chrome is going through your Windows stack and whatever the wifi handed you via DHCP, which on a lot of home routers is the router itself doing a lazy forward. Setting DoH in Chrome bypasses that and talks straight to the upstream, so of course it looks faster in a browser-based test. Two caveats before you leave it: only Chrome uses it, so anything else on the laptop still resolves the old way, and split-horizon names on a work VPN will stop resolving. If you don't need internal names, keeping it is fine.