After installing Firefox 123.0 I ran a Mullvad Connection check https://mullvad.net/en/check and found I had a DNS leak. Turns out that Firefox had changed the settings under “DNS over HTTPS” so that my Mullvad DNS wasn’t being used any more. After changing this setting to “off” in Firefox, the Mullvad check passed.
You must log in or register to comment.
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 2.42K Posts
- 56.9K Comments
- Modlog
That should be more secure and private
Note that this isn’t really a DNS leak. DoH is also going through the VPN proxy, so no data is leaked anywhere here.
What the “DNS leak test” does is to check whether you’re using Mullvad’s DNS servers. That’s it. It doesn’t and cannot actually check whether or not your DNS requests happen through the proxy or not.
My Firefox DNS over HTTPS settings are as they were before the upgrade. Maybe this is Flatpak-specific?
I should have mentioned, I am running the Flatpak version of Firefox on Kubuntu 23.10
In my case the setting stayed off after upgrade.