UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3053.3 Safari/537.36

Steps to reproduce the problem:
Currently, it's not possible to configure VPN such that public DNS names are resolved against the public interface’s DNS servers, while private DNS names should be resolved over the VPN tunnel.

What is the expected behavior?
We are looking for an enhancement like this to the chrome.vpnProvider API:

Support a “splitDNSDomains” field in setParameters. This is an array of strings that will be matched against a DNS query to determine whether it should be resolved inside the tunnel or outside. If empty, it reverts to the default (current) behavior, which is to choose based on the routing policy.

What went wrong?
Nothing. This is an enhancement request

Did this work before? No 

Does this work in other browsers? N/A

Chrome version: 59.0.3053.3  Channel: n/a
OS Version: 9334.10.0
Flash Version:
 

Deleted: split_dns.txt 348 bytes

split_dns.txt 348 bytes View Download