Joined: 18 Mar 2014 Posts: 6206 Location: Netherlands
Posted: Sun May 12, 2019 16:52 Post subject:
I think one of the things which must be made crystal clear is what you (and I) are defining as a DNS leak, not only using the "wrong" DNS server but also sending the DNS query out in the open via the WAN interface.
When the VPN provider pushes a private IP address as DNS server and the router is of the VPN, I think that the router does not have sufficient routing information to route that private IP address via the VPN so it will not work in most cases?
A solution in these cases can be if you can use destination based routing and thus can instruct the OVPN client to route that specific IP address via the VPN
Thank you for this script , it has been a blessing and a curse at the same time please allow me to explain , with my old ISP provider I had lan->lan connection for NBN connection and the setup was WAN Connection Type: Static IP which worked and showed no dnsleak with your dnsleak test script, great. Now though I have change ISP provider and this time setting are different , LAN->WAN and the WAN Connection Type: Automatic Configuration it's working though dnsleak test script is showing "user.warn ddwrt-ultimate-dns-leak: dns leak detected" repeatedly , I can't for some reason use the "no-reslov" in dnsmasq config section as this block internet browser usage but connection to the internet show in the log. There does not seem to be and issue with non vpn connection however VPN connection is a real problem.