Avatar for Username

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Тази тема беше архивирана. Моля, задайте нов въпрос ако имате нужда от помощ.

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

  • 2 отговора
  • 1 има този проблем
  • 5 изгледи
  • Последен отговор от Jason R. Coombs

Jason R. Coombs
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?

Всички отговори (2)

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Hi

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

Jason R. Coombs
Jason R. Coombs Задаващият въпроса
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).