Closed Bug 1810362 Opened 1 year ago Closed 2 months ago

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

Categories

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

Firefox 110
x86_64
Windows 11
defect

Tracking

()

VERIFIED FIXED
126 Branch
Tracking Status
firefox126 --- verified

People

(Reporter: selim, Assigned: serfreeman1337)

References

(Blocks 3 open bugs)

Details

(Whiteboard: [necko-triaged])

Attachments

(6 files)

Attached image 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:

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.

Attached image test-ipv6.com Firefox
Attached image ipv6-test.com Edge
Attached image test-ipv6.com Edge

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!

Blocks: IPv6
Severity: -- → S3
Flags: needinfo?(selim)
Priority: -- → P2
Whiteboard: [necko-triaged]
Attached file HTTP logs

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

Flags: needinfo?(selim)

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.

Blocks: dns
Duplicate of this bug: 1878445

Bug 1874094 and bug 920367 also seem related to this.

See Also: → 920367, 1874094

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

Assignee: nobody → serfreeman1337
Status: NEW → ASSIGNED

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

Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 126 Branch
Flags: qe-verify+

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?

Flags: needinfo?(selim)

I can confirm that it's fixed.

Flags: needinfo?(selim)

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

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: