IPv4 prioritized over IPv6 for local server
Categories
(Core :: Networking: DNS, enhancement, P2)
Tracking
()
People
(Reporter: net, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged][necko-priority-next])
Steps to reproduce:
I connect to a webserver (nginx) running on the local machine via Firefox, using a DNS server on my LAN to resolve the local machine's address.
Actual results:
The local machine's IPv4 address gets consistently prioritized over IPv6. This does not happen if the address is resolved via /etc/hosts (::1, 127.0.0.1), but only when resolving through the DNS server.
Safari and curl behave the same, and the curl team already confirmed that curl follows an (unexpected) ordering returned by getaddrinfo() in this case (s. https://github.com/curl/curl/issues/14761). The unexpected order can be illustrated with about:networking#dnslookuptool, e.g.
Domain: eden.internal (= local machine)
IPs
192.168.78.55
2001:908:531:baa0:10e0:6db1:72f1:2c2f
Domain: nuc.eden.internal (= different server)
IPs
2001:908:531:baa0:1e69:7aff:feaf:1455
192.168.78.42
Chrome, on the other hand, always prioritizes IPv6.
Expected results:
I expect IPv6 to get prioritized, as it is for all other webservers on my LAN.
|
||
Comment 1•5 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking: DNS' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Updated•5 months ago
|
+1 same issue here with FF and web servers having both IPV4 and 6, FF always goes with IPV4 :(
I have activated all options in about:config to get ff to be able to use IPV6 but still goes by default in IVP4 !
Description
•