搜索 | 用户支持

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

详细了解

Firefox conflict with Windows HTTPS (DoH) -> Requipred DoH

  • 2 个回答
  • 0 人有此问题
  • 1 次查看
  • 最后回复者为 Valentin

more options

When setting Windows to "Require DoH", firefox will not resolve DNS addresses, regardless of which "Enable secure DNS" setting is picked in FireFox security settings tab.

I expected at least "Off -- Use your default DNS resolver" to work.

If Windows is configured to just "Allow DoH", Firefox has no issues resolving DNS addresses, for any of the Firefox policy settings.

For reference, you can find the DoH policy setting in windows group policy editor, here:

gpedit.msc

Computer Configuration -> Administrative Templates -> Network -> DNS Client -> Configure DNS over HTTPS

(Have to enable it, then select Configure DoH options: Require DoH.)

you may need to issue a gpupdate /force for the setting to be picked up quickly.

When setting Windows to "Require DoH", firefox will not resolve DNS addresses, regardless of which "Enable secure DNS" setting is picked in FireFox security settings tab. I expected at least "Off -- Use your default DNS resolver" to work. If Windows is configured to just "Allow DoH", Firefox has no issues resolving DNS addresses, for any of the Firefox policy settings. For reference, you can find the DoH policy setting in windows group policy editor, here: gpedit.msc Computer Configuration -> Administrative Templates -> Network -> DNS Client -> Configure DNS over HTTPS (Have to enable it, then select Configure DoH options: Require DoH.) you may need to issue a gpupdate /force for the setting to be picked up quickly.

所有回复 (2)

more options

Here's a bit more information: ipv4 and ipv6 DNS server addresses are manually configured (say for 1.1.1.1) on the network interface. Microsoft Edge browser works fine at setting "Require DOH". nslookup also works fine at "Require DOH".

more options

I can reproduce the steps above. It seems Firefox's call to getaddrinfo is getting blocked when the policy is set to require DoH. I found that setting the DoH configuration in Settings (Win+I) > Network & Internet > Properties > DNS server > Manual > [Input cloudflare IPs] makes the policy configuration work.

I also found that Chrome also fails to resolve any domains if the policy is set to require DoH without configuring the appropriate server.

I'm not sure why the DNS resolution isn't getting blocked in Edge or nslookup, but not in Firefox or Chrome. I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1857473 to take a look at that, but ultimately I think this configuration is incorrect (require DoH policy without configuring the DoH servers)