1244282 - Download of firefox via IPv6 is not possible

Status: NEW

(Cloud Services :: Operations: Product Delivery, defect, P5)

Description

[grzchr15]

:: Developer Documentation Request

      Request Type: Correction
     Gecko Version: unspecified
 Technical Contact: 

:: Details

Name:    dn6m9t4qll5h.cloudfront.net
Address:  54.192.94.112
Aliases:  download-installer.cdn.mozilla.net

Firefox Downloads start at https://www.mozilla.org/en-US/firefox/new/ and use download-installer.cdn.mozilla.net for the actual downloads.

But this host is IPv4 only.

So, how to download /update Firefox from IPv6 only networks?

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

Nick, do you have any idea what this means?

Comment 2

[Nick Thomas [:nthomas] (UTC+12)]

Lets move this over to CloudOps, who run the product delivery stack these days.

download-installer.cdn.mozilla.net is for stub and full installers
download.cdn.mozilla.net is used by the built-in updater

Both seem to only support IPv4.

Comment 3

[Jeremy Orem [:oremj]]

Our CDNs do not currently support ipv6, but I'm sure they will at some time in the future.

Comment 4

[dagger.bugzilla]

It might help if you lean on them a bit. Although I thought Akamai supported v6?

I'd really like to see v6 support too, because I pay for my v4 traffic and Firefox downloads can easily eat quite a bit of it (especially when doing regression tests).

Comment 5

[Jake Maul [:jakem]]

Another issue: download.mozilla.org (aka bouncer) appears not to have a v6 record either.

Comment 6

[grzchr15]

2 years gone and still no Ipv6 on download.mozilla.org?

Comment 7

[grzchr15]

Just a progress step seen:
download-installer.cdn.mozilla.net. 59 IN CNAME dn6m9t4qll5h.cloudfront.net.
dn6m9t4qll5h.cloudfront.net. 59 IN      AAAA    2600:9000:2048:2800:e:19d6:1546:5981
dn6m9t4qll5h.cloudfront.net. 59 IN      AAAA    2600:9000:2048:e00:e:19d6:1546:5981
dn6m9t4qll5h.cloudfront.net. 59 IN      AAAA    2600:9000:2048:da00:e:19d6:1546:5981
dn6m9t4qll5h.cloudfront.net. 59 IN      AAAA    2600:9000:2048:800:e:19d6:1546:5981
dn6m9t4qll5h.cloudfront.net. 59 IN      AAAA    2600:9000:2048:1e00:e:19d6:1546:5981
dn6m9t4qll5h.cloudfront.net. 59 IN      AAAA    2600:9000:2048:ba00:e:19d6:1546:5981
dn6m9t4qll5h.cloudfront.net. 59 IN      AAAA    2600:9000:2048:be00:e:19d6:1546:5981
dn6m9t4qll5h.cloudfront.net. 59 IN      AAAA    2600:9000:2048:3e00:e:19d6:1546:5981
dn6m9t4qll5h.cloudfront.net. 59 IN      A       52.222.231.23

Comment 8

[grzchr15]

www.mozilla.org.        52      IN      CNAME   www.mozilla.org.cdn.cloudflare.net.
www.mozilla.org.cdn.cloudflare.net. 299 IN A    104.16.41.2
www.mozilla.org.cdn.cloudflare.net. 299 IN A    104.16.40.2
www.mozilla.org.        41      IN      CNAME   www.mozilla.org.cdn.cloudflare.net.
www.mozilla.org.cdn.cloudflare.net. 299 IN AAAA 2400:cb00:2048:1::6810:2802
www.mozilla.org.cdn.cloudflare.net. 299 IN AAAA 2400:cb00:2048:1::6810:2902


So only download.mozilla.org needs still some love?
download.mozilla.org.   34      IN      CNAME   bouncer-bouncer-elb.prod.mozaws.net.

Comment 9

[Isaac]

I was unable to download Firefox on my IPv6 only virtual machine. It's been 4 years and download.mozilla.org still doesn't have a AAAA record.

Comment 10

[sjw]

Since you've closed bug 1629830 we need at least a workaround for it. Can you share some options?

Comment 11

[Darkspirit]

Seen on Reddit: https://www.reddit.com/r/firefox/comments/gx1oiv/ipv6/
In worst case you could put Cloudflare in front of the current legacy-IP-only CDN.
https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-internet-facing-load-balancers.html

EC2-Classic
Load balancers in EC2-Classic support both IPv4 and IPv6 addresses. The console displays the following public DNS names:

name-123456789.region.elb.amazonaws.com
ipv6.name-123456789.region.elb.amazonaws.com    
dualstack.name-123456789.region.elb.amazonaws.com

The base public DNS name returns only IPv4 records. The public DNS name with the ipv6 prefix returns only IPv6 records. The public DNS name with the dualstack prefix returns both IPv4 and IPv6 records. We recommend that you enable IPv6 support by using the DNS name with the dualstack prefix to ensure that clients can access the load balancer using either IPv4 or IPv6.

Clients can connect to your load balancer in EC2-Classic using either IPv4 or IPv6. However, communication between the load balancer and its back-end instances uses only IPv4, regardless of how the client communicates with your load balancer.

Servo has a similar problem: https://download.servo.org just needs to point to https://servo-builds.s3.dualstack.us-west-2.amazonaws.com/index.html.

Comment 12

[fn84b]

archive.mozilla.org supports IPv6 (2600:1901:0:b9fd::). You can download Firefox installers from: https://archive.mozilla.org/pub/firefox/releases/