Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Why does enabling DNS over HTTPS (DoH) cause Firefox to prefer IPv4?

  • 2 respostas
  • 1 tem este problema
  • 5 visualizações
  • Última resposta de Jason R. Coombs

more options

I've enabled DoH by setting the `network.trr.mode` value to `2`. After restarting, I notice that websites are defaulting to IPv4. For example, browsing to http://kame.net shows a static turtle and not the animated one. Switching the mode back to `0` and restarting, the site resolves to IPv6. I tried enabling `network.trr.early-AAAA` in the hopes that would restore a preference for IPv6, but no luck.

Is there a way to enable DoH without degrading the default IP stack to IPv4?

I've enabled DoH by setting the `network.trr.mode` value to `2`. After restarting, I notice that websites are defaulting to IPv4. For example, browsing to http://kame.net shows a static turtle and not the animated one. Switching the mode back to `0` and restarting, the site resolves to IPv6. I tried enabling `network.trr.early-AAAA` in the hopes that would restore a preference for IPv6, but no luck. Is there a way to enable DoH without degrading the default IP stack to IPv4?

Todas as respostas (2)

more options

Hi

If you change the network.trr.mode to 3 it should force DoH regardless of site.

more options

Hi Seburo. I don't see how that suggestion at all addresses my concern. My issue is that when enabling DoH, it seems that the preference for IPv6 is lost and IPv4 is preferred, despite the behavior being different with DoH disabled.

I did try your suggestion to use mode 3, but at least in my current environment, it fails to resolve the addresses at all (possibly due to corporate restrictions).