I just signed up with Mullvad as my current NordVPN subscription is coming to an end.
By using the NordVPN provider based option in app I can successfully connect and override/bypass Nord's DNS by providing my own preferred DNS server.
However with Mullvad I am unable to bypass their DNS servers as per the above method within the passepartout app. I can verify by dnsleaktest.com
I am trying to override the DNS to my AdGuard Home server (which works with Nord), but you can test with google 22.214.171.124 and Mullvad and verifying on dnsleaktest.com
If I unmask the network data and view the debug log I can see a dozen lines below 'starting tunnel' the following 'DNS: ["126.96.36.199"].
I have managed to find a workaround (confirmed) however it involves downloading the openVPN config from the Mullvad webpage and manually modifying the UDP port to allow overriding the DNS in the passepartout app. Mullvad support advised the following
You would need to connect to port 1400 UDP or 1401 TCP as well, since on
the default ports we hijack the DNS requests.
I am aware that in the passepartout app I can select a number of pre-defined ports for UDP and TCP (however the above ports are not an option for Mullvad). But as a means to simplify this going forward is it possible that the app could provide an option for the above ports? Or alternatively, if a user using Mullvad via the providers section of the app decides to override the DNS, then passepartout app will automatially modify the UDP or TCP port to allow third party DNS servers?
It would be convenient going forward and much more simpler than manually modifying the config file once downloaded from Mullvad.
Hi @keeshux! Wasn't sure if I should open a new issue but for context I will raise it here for now.
The custom DNS works great after applying it after updating the infrastructure. But after reboot of my iPhone the custom DNS preset no longer appears as an option. It basically reverts to how it was previously prior to when you asked me to do the infrastructure update.
To workaround I just need to update the infrastructure again - but I need to remember this after reboot.