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

搜尋 Mozilla 技術支援網站

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

了解更多

dns over https configuration issue

more options

If I place in the /general/network settings/ -Enable DNS over https the value of "https://mozilla.cloudflare-dns.com/dns-query" and place a fake DNS server IP on my workstations DNS such as 100.100.100.100 (not a DNS server) as apposed to 8.8.8.8 should Firefox be able to resolve network sites?

I had this configuration initially and it worked then stopped today Nov-26-2018. See below configuration from firefox and cloudflares "https://cloudflare-dns.com/help/" test.

If I place in the /general/network settings/ -Enable DNS over https the value of "https://mozilla.cloudflare-dns.com/dns-query" and place a fake DNS server IP on my workstations DNS such as 100.100.100.100 (not a DNS server) as apposed to 8.8.8.8 should Firefox be able to resolve network sites? I had this configuration initially and it worked then stopped today Nov-26-2018. See below configuration from firefox and cloudflares "https://cloudflare-dns.com/help/" test.
附加的畫面擷圖

被選擇的解決方法

I have found a solution. DNS over https ddoes not rely on the workstations local DNS as long as network.trr.mode is set to a value of 3. If network.trr.mode is set to 2 you cannot tell as it will fal back to your hosts DNS if a resolution failure occurs

從原來的回覆中察看解決方案 👍 0

所有回覆 (2)

more options

mace2 said

If I place in the /general/network settings/ -Enable DNS over https the value of "https://mozilla.cloudflare-dns.com/dns-query" and place a fake DNS server IP on my workstations DNS such as 100.100.100.100 (not a DNS server) as apposed to 8.8.8.8 should Firefox be able to resolve network sites? I had this configuration initially and it worked then stopped today Nov-26-2018. See below configuration from firefox and cloudflares "https://cloudflare-dns.com/help/" test.

I have noticed that firefox 63.03 will no long resolve requests immediately after a clear history of all components is performed. Is this a known bug?

more options

選擇的解決方法

I have found a solution. DNS over https ddoes not rely on the workstations local DNS as long as network.trr.mode is set to a value of 3. If network.trr.mode is set to 2 you cannot tell as it will fal back to your hosts DNS if a resolution failure occurs