1810362 - Firefox does not seem to support IPv6 unless DNS-over-HTTPS is enabled

Status: RESOLVED FIXED

(Core :: Networking: DNS, defect, P2)

Description

[Selim Şumlu]

Attachment: ipv6-test.com Firefox

My ISP has recently enabled IPv6 and I've configured my home network accordingly.

However, all of the tests listed below fail to detect full IPv6 support on Firefox with default settings:

• https://test-ipv6.com/ ("Your browser has real working IPv6 address - but is avoiding using it.")
• https://ipv6-test.com/
• https://ipv6test.google.com/

Enabling DNS-over-HTTPS in Firefox settings and choosing Cloudflare as the server resolves the problem.

Configuring Windows 11 to use Cloudflare DoH system-wide does not resolve the problem, although navigating to https://1.1.1.1/help/ confirms that I'm connected to Cloudflare DoH.

I cannot reproduce this with Edge or Chrome. They seem to work fine with their default settings.

Comment 1

[Selim Şumlu]

Attachment: test-ipv6.com Firefox

Comment 2

[Selim Şumlu]

Attachment: ipv6-test.com Edge

Comment 3

[Selim Şumlu]

Attachment: test-ipv6.com Edge

Comment 4

[(PTO until Jan 6) Valentin Gosu [:valentin] (he/him)]

Could you capture some HTTP logs when not using DoH?
I'm thinking the problem might be that the native DNS doesn't give out IPv6? Or maybe there's some other bug?
https://firefox-source-docs.mozilla.org/networking/http/logging.html

Thanks!

Comment 5

[Selim Şumlu]

Attachment: HTTP logs

Here are two logs for ipv6test.google.com with DoH enabled and disabled.

Comment 6

[(PTO until Jan 6) Valentin Gosu [:valentin] (he/him)]

Thank you for the logs, very useful. It seems like the main difference between DoH and non-DoH is that for DoH we return the IPv6 addresses first, whereas for native DNS we don't - we just take them as they come from getaddrinfo.

We can probably just sort the addresses so the IPv6 ones come first. As far as I can tell, this has always been the behaviour of Firefox.
The AddrInfo object is created here.
We should probably sort them here. We should guard this by a pref, in case the preference for IPv6 starts causing other issues.

Comment 8

[Mark Banner (:standard8)]

Bug 1874094 and bug 920367 also seem related to this.

Comment 9

[serfreeman1337]

Attachment: Bug 1810362 - Sort the addresses in a DNS lookup result so the IPv6 ones come first. r=valentin

Introduce network.dns.preferIPv6 pref to place IPv6 addresses first in a DNS lookup result.

Comment 10

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/integration/autoland/rev/4f7031f621f979e50d20954ab1ce5407d3bb019b
Bug 1810362 - Sort the addresses in a DNS lookup result so the IPv6 ones come first. r=valentin,necko-reviewers,kershaw

Comment 11

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/4f7031f621f9

Comment 12

[Ina Popescu, Desktop QA]

Unfortunately I'm unable to verify this issue as I don't have access to an IPv6 connection. Selim Şumlu, could you kindly verify if the issue persists in the latest Firefox 126.0 version?

Comment 13

[Selim Şumlu]

I can confirm that it's fixed.

Comment 14

[Ina Popescu, Desktop QA]

Selim Şumlu, thank you for confirming.
Verified as fixed based on Comment 13.

Comment 16

[Selim Şumlu]

This seems to be broken again in the latest Nightly so I'm reopening this bug. Symptoms are the same.

Comment 17

[Selim Şumlu]

Quick update: Appearently this fix is now behind behind the network.dns.preferIPv6 pref, which is set to false by default. Toggling it to true fixes the issue.