Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

netdna.bootstrapcdn.com dont have ipv6 #533

Closed
Pedro-Miguel opened this issue Apr 17, 2015 · 13 comments
Closed

netdna.bootstrapcdn.com dont have ipv6 #533

Pedro-Miguel opened this issue Apr 17, 2015 · 13 comments
Labels

Comments

@Pedro-Miguel
Copy link

Hi,

1st off all sorry if this issue dont belong here.

No one can use bootstrap served via netdna.bootstrapcdn.com on Ipv6.

@jdorfman jdorfman added the todo label Apr 17, 2015
@jdorfman
Copy link
Member

Hey Pedro,

It is being worked on, we do not have an ETA as of now. I will follow up once it is deployed.

@anthonysomerset
Copy link

Is there any update on this? also includes DNS record maxcdn.bootstrapcdn.com

@jdorfman
Copy link
Member

jdorfman commented Oct 6, 2016

@anthonysomerset I wish I could give you an update. There are higher priorities at the moment. Don't get me wrong IPv6 is important, it hasn't been an issue with current customers.

@gsauthof
Copy link

gsauthof commented Feb 9, 2017

Can confirm, maxcdn.bootstrapcdn.com and oss.maxcdn.com still don't have AAAA records.

In contrast to that, e.g. ajax.googleapis.com has an AAAA record and works over IPv6.

@jdorfman
Copy link
Member

jdorfman commented Feb 9, 2017

@gsauthof you are correct, we still don't have AAAA records. I sent this to my contacts at MaxCDN/StackPath so it is on their radar.

gsauthof added a commit to gsauthof/voidy-bootstrap that referenced this issue Feb 9, 2017
Improvements:
- allow to easily override the used CDNs and still profit from SRI
- new default: switch from bootstrap-cdn to the cdnjs.com CDN because
  bootstrap-cdn doesn't support IPv6 (cf.
  jsdelivr/bootstrapcdn#533)
- switch from googleapis CDN to cdnjs.com as well - thus, by default
  one CDN is used for everything which can improve load times
  (think: connection re-use, pipelining)
@phillipremaker
Copy link

It's 2017 and still no IPv6. What's the progress and schedule?

@davecarlson
Copy link

AWS is IPv6 capable now - have you ensured it's enabled ?

For cloudfront, it's just a tickbox now !

screen shot 2017-12-12 at 11 56 54

@jdorfman
Copy link
Member

@davecarlson we don't use Cloudfront, StackPath is our CDN provider. No ETA when they are getting IPv6 support, but I can imagine soon since they are targeting enterprises.

@jdorfman
Copy link
Member

Starting today, we have begun testing IPv6 on a new platform/hostname: stackpath.bootstrapcdn.com

https://www.whatsmydns.net/#AAAA/stackpath.bootstrapcdn.com

In the next few weeks, the legacy hostnames (netdna, maxcdn, etc) will be moved over to the new platform.

@phillipremaker
Copy link

phillipremaker commented Mar 29, 2018 via email

@NiKiZe
Copy link

NiKiZe commented Jul 4, 2022

Any update on this? Could I suggest that you reopen this issue until IPv6 is resolved? Or is it some other issue that is still open covering this?

@jimaek
Copy link
Member

jimaek commented Jul 4, 2022

What endpoint are you talking about? stackpath.bootstrapcdn.com still works over ipv6

@NiKiZe
Copy link

NiKiZe commented Jul 4, 2022

What endpoint are you talking about? stackpath.bootstrapcdn.com still works over ipv6

I encountered maxcdn.bootstrapcdn.com in the wild where IPvFoo showed v4 while everything else was v6.
Can not reproduce now, so probably a bad cache for some reason. Sorry for the noise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants