New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 516305 link

Starred by 7 users

Issue metadata

Status: Available
Owner: ----
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Sign in to add a comment

Chrome not respecting ipv6 prefix precedence on linux.

Reported by, Aug 3 2015

Issue description

Chrome Version       : 44.0.2403.125 (Official Build) (64-bit)
URLs (if applicable) :
Other browsers tested:
     Safari: Not available on linux.
    Firefox: Yes, prefix precedence is respected.
         IE: Not available on linux.

What steps will reproduce the problem?
1. Get ipv6 address space of, and give it with lowest precedence (lower than ::ffff:0:0/96) in /etc/gai.conf.
2. Open
3. Go to chrome://net-internals and check for connect jobs.

What is the expected result?
Connect to via ipv4.

What happens instead?
Connect to via ipv6.

Please provide any additional information below. Attach a screenshot if

Screenshot to net-internals, and my /etc/gai.conf is attached.
221 KB View Download
2.6 KB Download
Labels: Cr-Internals-Network-DNS OS-Linux
If you launch chrome with --disable-async-dns does it work as expected?

(Presumably this is a problem with how Chrome's internal DNS sorts the addresses)
Labels: Needs-Feedback

Comment 4 by, Aug 5 2015

Yes, it work as expected. So this is likely to be a problem with async dns client, which didn't respect ipv6 prefix precedence.
278 KB View Download

Comment 5 by, Aug 5 2015

Socket connection also shows using ipv4 as expected.
374 KB View Download

Comment 6 by, Aug 9 2015

Any update for this issue?
And more, I think this bug can be reproduced on all platforms, since internal async-dns client didn't respect ipv6 prefix precedence at all.
Labels: -Needs-Feedback OS-Chrome
Status: Available
Labels: -OS-Chrome

Comment 10 by, Aug 19 2016

So... this issue is getting ignored then? For users with non-native ipv6 it's a bit of a requirement to be able to change precedence. For example, youtube doesn't accept any payments unless I disable ipv6 (due to 6in4 tunnel exiting in the neighboring country with different currency). That's not even touching latency issues.

Please, could someone show this issue some love?
The disable-async-dns flag has been removed, as requested and discussed in  Issue 432236 , 

So to my knowledge there is no workaround left around Chrome's ignorance towards standards.

gai.conf shouldn't even be needed to prioritize IPv4 over IPv6 if the IPv6 address is in a range that by it's very definition is a heavily detoured connection.

Owner: ----
For some reason starting from version 69.0.3497.81 Chromium in Ubuntu started ignoring /etc/gai.conf. This is a disaster.

Sign in to add a comment