And domains like `files.pythonhosted.org` cannot be resolved from DNS servers within IPv6 only networks.
ns1.fastly.net has address 23.235.32.32
ns2.fastly.net has address 104.156.80.32
ns3.fastly.net has address 23.235.36.32
ns4.fastly.net has address 104.156.84.32
Is there any plans to IPv6 support for the fastly nameservers?
Hey @miyuru, since this is about one of our customers, we can’t go into specifics. But the PSF manages its work in public (hence the GitHub issues), so we have a little more leeway. We can reach out to them to make sure they’re on the latest version of our platform.
this issue applies to all of your customers who uses cname.
even jsdelivr gets affected when it uses fastly. (I am aware that they use mutiple CDNs)
None of the fastly dot net nameservers have AAAA records.
$ dig +short fastly dot net ns
ns3 dot fastly dot net.
ns4 dot fastly.net.
ns1 dot fastly.net.
ns2 dot fastly.net.
$ dig +short ns1.fastly.net aaaa
$
wikimedia rolled out IPv6 for AuthDNS servers today.
If any fastly engineers want pointers, see the discussion here.
