download.zfsonlinux.org not accessible via IPv6

Open
#111 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws
Domain
cloud, networking

Research direction

Start by checking the DNS configuration for download.zfsonlinux.org and compare the current S3 website endpoint with the dual-stack endpoint named in the issue. Done means the RPM repositories are reachable by IPv6-only systems, either through the existing domain or a documented separate domain.

Written by the indexing model from the issue text.

Description

Unfortunately, the official download option for Source RPMs (download.zfsonlinux.org) is not accessible via IPv6, but only via IPv4. This is because only a CNAME for an IPv4-only service is stored in the DNS.

$ host download.zfsonlinux.org
download.zfsonlinux.org is an alias for download.zfsonlinux.org.s3-website-us-west-2.amazonaws.com.
download.zfsonlinux.org.s3-website-us-west-2.amazonaws.com is an alias for s3-website.us-west-2.amazonaws.com.
s3-website.us-west-2.amazonaws.com has address 3.5.80.31
s3-website.us-west-2.amazonaws.com has address 52.92.207.91
s3-website.us-west-2.amazonaws.com has address 3.5.83.183
s3-website.us-west-2.amazonaws.com has address 52.92.229.67
s3-website.us-west-2.amazonaws.com has address 52.92.239.107
s3-website.us-west-2.amazonaws.com has address 52.92.227.227
s3-website.us-west-2.amazonaws.com has address 3.5.82.151
s3-website.us-west-2.amazonaws.com has address 3.5.81.217

This means that the RPM repositories cannot be accessed by IPv6-only systems. To my knowledge, there is a dual-stack equivalent for s3-website.us-west-2.amazonaws.com: s3-website.dualstack.us-west-2.amazonaws.com. Would it be possible to switch to this or at least offer the option of accessing it via IPv6 using a separate domain?

Dominant language
HTML
Stars
72
Forks
36
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from zfsonlinux/zfsonlinux.github.com

All issues in zfsonlinux/zfsonlinux.github.com

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.