Secure DNS doesn't work after connecting to ProtonVPN

Description of the issue:
How can this issue be reproduced?

  1. Connect to ProtonVPN
  2. Try and visit any website
  3. Receive error, " This site can’t be reached www.google.com’s DNS address could not be found. Diagnosing the problem. DNS_PROBE_POSSIBLE"
  4. Go to brave://settings/security?search=dns
  5. CHANGE the Secure DNS provider (from any, to any), and now DNS resolution works. (Note this assumes that “Use Secure DNS” is on)

Expected result:

DNS should keep resolving websites after connecting to VPN without having to manually switch DNS provider.

Brave Version( check About Brave):

[Version 1.74.51 Chromium: 132.0.6834.160 (Official Build) (arm64)]

Additional Information:

I am not sure if this is an issue only with ProtonVPN, or possibly ANY VPN.

I manually enter DNS servers. On network routers, computing devices.

Ranking the IP address numbers:

  • VPN DNS server
  • VPN DNS server
  • ISP or Local Wi-Fi DNS Server
  • ISP or Local Wi-Fi DNS Server

Manually set DNS server numbers:

Best free or public DNS servers - Quick list:

https://privacysavvy.com/security/business/best-free-public-dns-servers/

How to change DNS settings on your PC running Windows 10

https://www.windowscentral.com/how-change-your-pcs-dns-settings-windows-10

How to change DNS settings on your Linux machine

https://www.linux.org/threads/question-on-manually-setting-my-dns-server-address.53227/

Change DNS settings on Mac

https://support.apple.com/guide/mac-help/change-dns-settings-on-mac-mh14127/mac


DNS servers on my computer don’t seem to be the issue, it’s the “Secure DNS” option in Brave.

I am also receiving this issue frequently now.

I have Proton VPN installed as an extension in Brave that I sometimes use but I also have Proton VPN installed as a desktop application for Mac that I sometimes use. I am not immediately recalling if this error is happening anytime I connect to Proton VPN (either the browser extenstion or the desktop app version) or if I receive the error only when connecting to the extension (or vice-versa).

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.