X
點擊此處開啟此網站的行動版。

技術支援討論區

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.

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

額外的系統細節

應用程式

  • User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.1 Safari/605.1.15

更多資訊

jscher2000
  • Top 10 Contributor
8767 個解決方法 71704 個答案

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.

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.''
這篇文章有幫助嗎?
引用

提出問題者

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:

''jscher2000 [[#answer-1260180|said]]'' <blockquote> 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.'' </blockquote> 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 於 修改

這篇文章有幫助嗎?
引用
jscher2000
  • Top 10 Contributor
8767 個解決方法 71704 個答案

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.

''RubberDucky [[#answer-1260211|said]]'' <blockquote> Would I put cloudflares dns address in the network.trr.bootstrapAddress ? I enabled dns over https in the options page. </blockquote> 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.
這篇文章有幫助嗎?
引用
jscher2000
  • Top 10 Contributor
8767 個解決方法 71704 個答案

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.

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.
這篇文章有幫助嗎?
引用
問個問題

如果您還沒有帳號,您必須先 登入您的帳號 來回覆文章。請 開始一個新問題