Allow ProtonVPN to use existing LAN DNS/Custom DNS
I run my own secure DNS. I would like for ProtonVPN to offer the ability for the user to elect to use an existing DNS / Custom DNS rather than the Proton DNS server. Private Internet Access, which I no longer use since changing to ProtonVPN, began offering that recently and it works well. There may be a security risk doing that but the user should be able to specify if they still want to do it. I would use my own DNS when on my LAN, and the Proton DNS when on a different network. Thank you.
Jeff
shared this idea
Available on Linux, Android, and Windows. Soon on iOS and macOS.
-
Anonymous
commented
Additionally my DNS is completely broken after running Proton VPN. I cannot reach anything even doing a flushdns doesn't help. Only fix is a reboot.
-
a
commented
Not working on Windows. I'm running a Unifi USG which points to a PiHole, and when connected to ProtonVPN all DNS requests are being directed to the VPN interface and its DNS servers, even when specifying the target DNS server explicitly at the command line.
-
SeraphTC
commented
Working on android, not on Linux. DNS requests are always routed via the VPN and the custom DNS address is ignored.
It's not split tunneling related, as the Linux client still doesn't have that feature.
-
Joe
commented
Custom DNS still cannot use local servers. I have a Pi-Hole and it's really frustrating that I can't use it while on Proton VPN. It works fine on Android, but there's something wrong with the Windows version. Private Internet Access has zero issues handling this.
-
Big Flubba
commented
This does not work (on Windows at least).
-
Anonymous
commented
@Gaupe it's frustrating because it doesn't work. They let you specify customized PUBLIC DNS addresses as the DNS traffic still is forced over the tunnel. Basically the Proton VPN client isn't adding together the results of a custom DNS setting AND the split tunnel setting.
-
Gaupe
commented
if its completed , then how does it work?
If ADMIN closes a request as completed then tell us how to do it. I can give my own local ip as dns server but it is not working (like 192.168.10.10) also not if i say in split tunnel that 192.168.10.0/24 is excluded via split tunneling -
Anonymous
commented
I opened a new feature request on this. https://protonmail.uservoice.com/forums/932836-proton-vpn/suggestions/49974234-local-dns-doesn-t-work-with-custom-dns
-
Anonymous
commented
Local DNS is not using the local interface correctly when paired with split tunnelling and custom DNS servers. Public/cloud DNS providers are reachable when placed in custom DNS but you cannot tell ProtonVPN to utilize the local DNS source on the local interface.
You can work around this by placing entries in the local hosts file but this is a small sub-set of the issue that can be worked around.
Old post where Proton Admin says this is resolved here: https://protonmail.uservoice.com/forums/932836-proton-vpn/suggestions/36087631-allow-protonvpn-to-use-existing-lan-dns-custom-dns
-
Anonymous
commented
Putting the name/IP combo of a local resource into the hosts file is a quick and dirty workaround to this, however, it ignores the larger problem of 1 resource not necessarily being the only thing that local DNS provider is identifying. This feature needs to be reconsidered.
-
Anonymous
commented
This doesn't work. When entering a local DNS source (split tunneling already omitting the entire local subnet) I don't receive a response from the local DNS server when testing.
It's almost as though split tunneling and custom DNS do not consider each other's combined functionality.
-
Zoltán Schmidt commented
Doesn't work for me either. I host a local Unbound DNS server in my home network for all the equipment, but the ones using ProtonVPN can't use it. Doesn't matter if it's added as a custom local DNS or added in split tunneling. The DNS host IP is reachable but as soon as the VPN is connected, the clients can't connect to the DNS port 53 anymore.
-
Mihails
commented
Doesn't work for me, after setting custom DNS to 192.168.x.x (also added as exception in split tunneling) DNS doesn't resolve any domain. As a result I can't access my local devices like Home Assistant instance via domain name which isn't in public DNS.
-
Chase
commented
It is still not working, even with the beta client. Using a local DNS server still breaks DNS resolution. Example, setting DNS to 10.1.0.23
-
ZAKO commented
Synthetic Card creation (Privacy.com)
-
Chase
commented
I use an internally hosted Pihole DNS, which is obviously a local IP address. It seems the ProtonVPN app cannot use internal DNS servers.
Private Internet Access works great for this situation with their option to "Use existing DNS" If ProtonVPN offered this, I'd upgrade to Unlimited in a heartbeat.
-
Maurits
commented
Just make a separate service where we could choose our lists and settings similar to NextDNS.
-
trlrew
commented
Can't use Proton VPN in my local network because of it. Had to revert to Private Internet Access vpn.
-
Ephrum
commented
I echo this request. I too use PIA with my NextDNS account. When I link the IP from the VPN to NextDNS, the profile that I defined is then used, thereby blocking the trackers and malware that I have selected from the various databases. It also allows me to log my DNS traffic for my review. If there is a security risk, it would be good to know about, but it seems on the up and up.
-
Erik van Luxzenburg
commented
I see the option to choose a custom DNS in the Windows app but not in the Android and IOS apps. I would like to be able to choose my own DNS service for these apps as well. Or ProtonVPN should offer the option to block ads, tracking cookies and other privacy infringing technologies. Maybe you can take a look at NextDNS.io which offers these options to it's users.