It's possible that "Strict" also had a similar effect as "Exclusive" (as it was also a special case), causing the router's own resolv.conf to be empty.I use "Strict" on the limited by ip address clients which I wish to tunnel through to UK and "Relaxed" with a catch-all for the rest to Local VPN.
I'm reorganizing that part of the code to ensure that the system resolv.conf will always contain proper values, so only dnsmasq's own servers will be skipped. I'm also tightening requirements for this to happen. The expected final result will be:
- If at least one client is running, and it has DNS mode set to Exclusive, and it's set in "Redirect All", then skip adding WAN DNS servers to dnsmasq
- Always have the router's own resolv.conf contain WAN nameservers, regardless of VPN
Either nobody used it recently, or they somehow had it set so it just worked without triggering the issues (for example if they only configured that one client, and kept the DNS mode to the default value). However now that it will more reliably truly redirect WAN traffic (or not redirect it if set to "No"), I believe it's worth the effort of fixing it.Simple solution ... if nobody uses Redirect = "(Yes All)" anymore - just dump it as an option
Dnsmasq's configuration changed a lot over the years, and I suspect that gradually the OpenVPN DNS management started to develop issues of its own following these changes. This might have gotten worse when I redesigned a lot of the OpenVPN implementation during the last 384.xx releases, but it only got noticed just now as we've all been poking at OpenVPN's implementation during this test cycle.