Open Bug 1849143 Opened 1 year ago Updated 4 months ago

Firefox prefers IPv4 when website uses HTTPS DNS records with ipv4hints

Categories

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

Firefox 116
defect

Tracking

()

UNCONFIRMED

People

(Reporter: mozilla-bugzilla, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [necko-triaged][necko-priority-next])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0

Steps to reproduce:

  1. Enable DNS over HTTPS (preferably, specify the provider) which makes Firefox consult HTTPS records (for ECH, ALPN hints, IP hints)
  2. Get IPvFoo (https://addons.mozilla.org/en-US/firefox/addon/ipvfoo-pmarks/) to see what IP Firefox uses to connect
  3. Go into a website with HTTPS records that have IP hints (https://www.cloudflare.com)

(You might need to these flags to make sure Firefox uses HTTPS dns records: network.dns.force_use_https_rr, network.dns.force_waiting_https_rr)

Actual results:

Firefox ignored ipv6hints, only seemingly using ipv4hints to connect to the website which makes it use IPv4 in that website unless a true reload is performed even when IPv6 is available.

Expected results:

Firefox should've preferred IPv6 like it usually does when HTTPS records are not available. IPvFoo would've showed an IPv6 connection.

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Security' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → DOM: Security
Product: Firefox → Core
Component: DOM: Security → Networking: DNS
Severity: -- → S4
Priority: -- → P2
Whiteboard: [necko-triaged][necko-priority-review]
Blocks: IPv6
See Also: → 1874094
Whiteboard: [necko-triaged][necko-priority-review] → [necko-triaged][necko-priority-next]
See Also: → 1810362

The fix is currently behind the network.dns.preferIPv6 pref.
We should turn it on as soon as possible.

You need to log in before you can comment on or make changes to this bug.