john9527
Part of the Furniture
I apologize if I missed getting back to you. I remember your note and writing a reply (in fact I found where I had written and saved it). Your request came in about the time I had to have a 'double' root canal done, and I must have forgotten to hit send.I asked a couple of times about those settings but got no answer, didn't want to bother you again
Apparently I got my answer sideways eventually
Thanks
For everyone's benefit, here's the answer
The pulldown controls what DNS servers are used by dnsmasq. The checkbox option on the same line controls routing WAN clients' DNS requests to bypass dnsmasq and go directly to a different set of DNS servers in policy rules mode.
Accept DNS Configuration
- Disabled
The VPN DNS servers are ignored, and all clients use the current non-VPN servers via dnsmasq. - Relaxed
The VPN DNS servers are added to the list of servers that dnsmasq can use along with your default servers. Any server can be selected for any DNS request (will tend to use the fastest servers), so this can result in DNS leaks. DNSCrypt is not used even if configured. - Strict
The VPN DNS servers are prepended to the list of servers that dnsmasq can use followed by your default servers. DNS requests are sent to each server in order, starting with the VPN servers. If you have slow or poorly configred VPN servers, you will have DNS leaks. DNScrypt is not used even if configured. - Exclusive
The VPN DNS servers are the only servers used by dnsmasq. The checkbox option can change the DNS servers used by WAN clients, but then the WAN clients cannot use ABSolution. - DNSCrypt
If you have DNSCrypt configured, only the DNSCrypt servers are configured for use by dnsmasq. The checkbox option can change the DNS servers used by WAN clients, but then the WAN clients cannot use ABSolution.
Note that my implementation of 'Exclusive' is different from Merlin's. In Merlin builds with policy rules, 'Exclusive' uses dnsmasq for your default DNS servers/WAN clients, and VPN clients are automatically routed to bybass dnsmasq and go directly to the VPN DNS server. This is why under Merlin, VPN clients with Exclusive DNS set cannot make use of ABSolution (they don't use dnsmasq).
Alternatively, the downside to my implementation is that applications that hardcode requests to specific DNS servers, like Chromecast and google DNS, will have a leak to the google DNS server even if the Chromecast is in the VPN. If this is important to you, you can override the DNS handling with DNSFilter for those clients, but then those clients would loose the ability to use ABSolution.
But honestly, I've given up on trying to use VPNs on clients that are media players (unless you are using a VPN provider that specifically supports geo location hiding) . Applications like Netflix, Amazon Prime and other streaming apps now use the hardcoded DNS calls as part of their VPN/proxy checking and fail if you try and force the VPN DNS servers.