為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

VPN DNS Leak

  • 3 回覆
  • 0 有這個問題
  • 1 次檢視
  • 最近回覆由 Rebecca

more options

I've got Mozilla VPN on my macbook, but firefox shows DNS leaks when tested using https://mullvad.net/en/check/

Fixes already attempted: - DNS over HTTPS set custom provider to https://doh.mullvad.net/dns-query (from https://mullvad.net/en/help/dns-over-https-and-dns-over-tls/) - still leaking - using custom provider in about:config set network.trr.mode to 3 - no sites load - using custom provider set network.trr.mode back to 2 and set media.peer.connection.enabled to false - still leaking

Any suggestions?

I've got Mozilla VPN on my macbook, but firefox shows DNS leaks when tested using https://mullvad.net/en/check/ Fixes already attempted: - DNS over HTTPS set custom provider to https://doh.mullvad.net/dns-query (from https://mullvad.net/en/help/dns-over-https-and-dns-over-tls/) - still leaking - using custom provider in about:config set network.trr.mode to 3 - no sites load - using custom provider set network.trr.mode back to 2 and set media.peer.connection.enabled to false - still leaking Any suggestions?

所有回覆 (3)

more options

Have you gone through their FAQ site yet?

https://www.mozilla.org/en-US/products/vpn/

more options

Rebecca said

I've got Mozilla VPN on my macbook, Any suggestions?

You should post this in the Mozilla VPN section using https://support.mozilla.org/en-US/questions/new/firefox-private-network-vpn/form since it is a premium product. (as listed on https://support.mozilla.org/questions/new}

more options

James said

Rebecca said

I've got Mozilla VPN on my macbook, Any suggestions?

You should post this in the Mozilla VPN section using https://support.mozilla.org/en-US/questions/new/firefox-private-network-vpn/form since it is a premium product. (as listed on https://support.mozilla.org/questions/new}

This is specifically a firefox issue, as neither safari nor chrome are showing dns leaks.