We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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

搜索 | 用户支持

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

详细了解

Will not connect to server unless I disable dns-over-https in settings, then re-enable it on new launch of Firefox browser.

more options

Will not connect to server unless I disable dns-over-https in settings, then re-enable it on new launch of Firefox browser.

Will not connect to server unless I disable dns-over-https in settings, then re-enable it on new launch of Firefox browser.

所有回复 (4)

more options

Hi RubberDucky, what's the specific error message you get when Firefox can't connect to anything?

Are you enabling DNS over HTTPS through the Preferences page, or are you manually modifying settings in about:config? If you are manually modifying one or more settings, what values are you using?


The reason I ask that is Firefox has multiple modes for DNS over HTTPS, and some will "fall back" to the standard method of looking up addresses when they can't reach the "trusted resolver" and some will not (and therefore must fail). By default, enabling DNS over HTTPS through the Preferences page sets network.trr.mode = 2, which allows fallback. If you manually set network.trr.mode = 3, then you likely will need to also set network.trr.bootstrapAddress in order to allow Firefox to look up the address of the trusted resolver.

more options

jscher2000 said

Hi RubberDucky, what's the specific error message you get when Firefox can't connect to anything? Are you enabling DNS over HTTPS through the Preferences page, or are you manually modifying settings in about:config? If you are manually modifying one or more settings, what values are you using?

The reason I ask that is Firefox has multiple modes for DNS over HTTPS, and some will "fall back" to the standard method of looking up addresses when they can't reach the "trusted resolver" and some will not (and therefore must fail). By default, enabling DNS over HTTPS through the Preferences page sets network.trr.mode = 2, which allows fallback. If you manually set network.trr.mode = 3, then you likely will need to also set network.trr.bootstrapAddress in order to allow Firefox to look up the address of the trusted resolver.


Would I put cloudflares dns address in the network.trr.bootstrapAddress ?

I enabled dns over https in the options page.

And this is the error I get:

由RubberDucky于修改

more options

RubberDucky said

Would I put cloudflares dns address in the network.trr.bootstrapAddress ? I enabled dns over https in the options page.

If you enable DNS over HTTPS using the Options page, then you should find the value set to 2 here:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button accepting the risk.

(2) In the search box above the list, type or paste trr and pause while the list is filtered

(3) If the network.trr.mode preference is not set to 2 you can double-click it to edit the value to 2 and then click OK

If network.trr.mode is set to 3 then the bootstrap address will depend on which resolver you use. For Cloudflare, I think the bootstrap address is 1.1.1.1 so you could try that.

more options

By the way, some network administrators might block DNS over HTTPS because it interferes with their filtering. On one of those networks, you'll need to use normal address resolution.