Chrome not using VPN DNS (Everything else is)


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:

enter image description here


Related videos on Youtube

Kyle Brandt
Author by

Kyle Brandt

Updated on September 18, 2022


  • Kyle Brandt
    Kyle Brandt 9 months

    DNS in chrome is not using my VPN DNS:

    1. Things that should match private vpn DNS records are instead resolving again a public wildcard address
    2. This only seems to happen in Chrome, iterm pings and firefox resolve correctly
    3. 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
    4. Going to a website via IP in Chrome works fine
  • renrutsirhc
    renrutsirhc almost 10 years
  • Karl Wilbur
    Karl Wilbur about 8 years
    The "Built-in Asynchronous DNS" flag was removed from Google Chrome, thereby disabling the "fix" for this.…
  • backtabber
    backtabber over 4 years
    @bertieb Thanks for bringing this to my attention.
  • foucdeg
    foucdeg about 4 years
    I don't see that flag in chrome://flags, can it still be disabled?