1
Virtual private networks / Re: DNSCrypt and Wireguard - Internal resolver bypassed
« on: February 22, 2022, 10:07:53 pm »
I kept troubleshooting, and no luck so far.
I have tried to delete the DNSes under General, specify the internal LAN address as DNS for DHCP Server, using Unbound and checking that the ACL are set up properly, etc but the issue is still there.
The issue is also present with devices outside the tunnel!
It's like the Wireguard plugin, since there are no specified DNSes in the Local conf, it's pushing whatever DNS is getting from the tunnel (the destination ISP in this case) to the entire network.
I tried to specify Quad9 DNSes in the WG Local conf, and it works ONLY for devices outside the VPN and with some leaks: I get Quad9 DNSes but also the ISP DNSes. For devices INSIDE the VPN same thing, only the DNS from the ISP.
With this configuration I also loose the ability to use blacklist, the cache of the internal resolver, and the advantages of DoH/DoT.
Hoping for ideas here.
I have tried to delete the DNSes under General, specify the internal LAN address as DNS for DHCP Server, using Unbound and checking that the ACL are set up properly, etc but the issue is still there.
The issue is also present with devices outside the tunnel!
It's like the Wireguard plugin, since there are no specified DNSes in the Local conf, it's pushing whatever DNS is getting from the tunnel (the destination ISP in this case) to the entire network.
I tried to specify Quad9 DNSes in the WG Local conf, and it works ONLY for devices outside the VPN and with some leaks: I get Quad9 DNSes but also the ISP DNSes. For devices INSIDE the VPN same thing, only the DNS from the ISP.
With this configuration I also loose the ability to use blacklist, the cache of the internal resolver, and the advantages of DoH/DoT.
Hoping for ideas here.