为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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