Chrome not using VPN DNS (Everything else is)
8,530
For some reason using the "Built-in Asynchronous DNS" was not selecting my VPN DNS servers. I could see that the VPN DNS server was not being used via chrome://net-internals/#dns
. As a workaround, I disabled this via chrome://flags
:
Related videos on Youtube

Author by
Kyle Brandt
Updated on September 18, 2022Comments
-
Kyle Brandt 9 months
DNS in chrome is not using my VPN DNS:
- Things that should match private vpn DNS records are instead resolving again a public wildcard address
- This only seems to happen in Chrome, iterm pings and firefox resolve correctly
- clearing the host cache via
chrome://net-internals/#dns
doesn't help, not does clear all cache via settings. Restarting Chrome also doesn't seem to help - Going to a website via IP in Chrome works fine
-
renrutsirhc almost 10 yearsFYI: This is a known issue: code.google.com/p/chromium/issues/detail?id=265970
-
Karl Wilbur about 8 yearsThe "Built-in Asynchronous DNS" flag was removed from Google Chrome, thereby disabling the "fix" for this. chromium.googlesource.com/chromium/src/+/…
-
backtabber over 4 years@bertieb Thanks for bringing this to my attention.
-
foucdeg about 4 yearsI don't see that flag in chrome://flags, can it still be disabled?