Issue metadata
Sign in to add a comment
|
Chrome "Async DNS Prefetch" feature does not honor VpnService DNS server.
Reported by
logan9...@gmail.com,
Jan 29 2018
|
||||||||||||||||||||||||
Issue descriptionExample URL: Steps to reproduce the problem: 1. Setup a VpnService using VpnService.Builder. 2. Add a DNS server using `addDNSServer( String address )`. 3. Browse in Chrome using new "Async DNS Prefetch" feature. What is the expected behavior? All traffic on the Android device, including Chrome's, will always use the VpnService DNS server. What went wrong? Chrome does not always use the VpnService DNS server. Did this work before? N/A Chrome version: 64.0.3282.123 Channel: stable OS Version: Any Flash Version: In the attached pcap, perform a filter on DNS packets. Our VpnService has local IP of 10.8.0.1 and DNS server set to 8.8.8.8. Notice that all DNS lookups are performed using the IP of system DNS, that of my wireless router DHCP server, which then decides what DNS server to use.
,
Jan 29 2018
Thanks for making a bug report! We turned off the feature for stable channel a few days ago because of this bug, so it should go away if you restart your browser, unless you enabled it manually in chrome://flags.
,
Jan 29 2018
Great! This has caused many issues for our users, with the need of our specific DNS server settings. Thank you. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by b...@chromium.org
, Jan 29 2018Components: -Internals>Network Internals>Network>DNS Internals>Network>VPN