Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox inbuilt VPN does not work with DNS over HTTPs enabled with Max Protection enabled

  • 2 replies
  • 1 has this problem
  • 63 views
  • Last reply by jbr
  • Solved

Trotter999
Trotter999

The VPN works if I Enable DNS over HTTPS using Default Protection, however if I select Max Protection and use Cloudflare, it does not work as it cannot resolve DNS.

If I disable the VPN or select Defualt Protection, DNS works again.

Windows 11 Pro 25H2 26200.8313 Firefox 150.0.1

The VPN works if I Enable DNS over HTTPS using Default Protection, however if I select Max Protection and use Cloudflare, it does not work as it cannot resolve DNS. If I disable the VPN or select Defualt Protection, DNS works again. Windows 11 Pro 25H2 26200.8313 Firefox 150.0.1
Attached screenshots

Chosen solution

Thanks for the investigations. Normally there are some exceptions so it's interesting the features don't check each other's presence or mention the mitigation options in the error message. I've seen similar feedback on Mozilla Connect but wasn't able to find any bug filed on that topic, so there's now one by another reporter: https://bugzilla.mozilla.org/show_bug.cgi?id=2037364 if you want to follow any updates.

Thanks for reporting this!

Read this answer in context 👍 0

All Replies (2)

Trotter999
Trotter999 Question owner

It looks like enabling the Firefox VPN and having DNS over HTTPs enabled could cause issues, hence why it does not work. Possibly Firefox should disable DNS over HTTPs when the VPN is active, and enable it again when the VPN is stopped.

jbr
jbr

Chosen Solution

Thanks for the investigations. Normally there are some exceptions so it's interesting the features don't check each other's presence or mention the mitigation options in the error message. I've seen similar feedback on Mozilla Connect but wasn't able to find any bug filed on that topic, so there's now one by another reporter: https://bugzilla.mozilla.org/show_bug.cgi?id=2037364 if you want to follow any updates.

Thanks for reporting this!

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.