Şu anda bakım nedeniyle sitemiz kısıtlı işlevsellik sunmaktadır. Mevcut makaleler sorununuzu çözmediyse ve bize soru sormak isterseniz Twitter’da @FirefoxSupport hesabından ve Reddit’teki /r/firefox subreddit'inden destek gönüllülerimize ulaşabilirsiniz.

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

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

  • 2 yanıt
  • 1 kişi bu sorunu yaşıyor
  • 5 gösterim
  • Son yanıtı yazan: 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?

Tüm Yanıtlar (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).