Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
A few questions about jsDelivr
See original GitHub issueRecently I have noticed that cdn.jsdelivr.net has shorten the CNAME chain.
$ dig cdn.jsdelivr.net @1.0.0.1 +short CNAME
cdn.jsdelivr.net.cdn.cloudflare.net.
$ dig cdn.jsdelivr.net @8.8.8.8 +short CNAME
cdn.jsdelivr.net.cdn.cloudflare.net.
It seems that cdn.jsdelivr.net no longer uses PerfOps as load balancer. So is there any technical details about this change? Are jsDelivr simply using GeoDNS provided by NS1 & CloudNS? Also, StackPath & Fastly no longer shown up in DNS Propagation Map. Is the jsDelivr no longer considered using Fastly & StackPath.
Another problem is jsDelivr has down in China last year due to expired SSL certificate (#18148). Since cdn.jsdelivr.net has valid ICP License, is it possible to use both Cloudflare’s China Network & QUANTIL in China? jsDelivr is using Cloudflare Universal SSL which could be auto renewed, which means jsDelivr could use Cloudflare’s China Network as a failover in case SSL at QUANTIL expired again.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
For now it’s based on static data and Fastly is used in locations where it’s consistently better. Eventually we will move to another real-time LB solution.
I see, nice. Keep us posted if you think there is anything we could improve