Hey there, Cloudflare user!
Have you ever considered trying QUIC.cloud CDN but then you just didn’t?
Maybe you were concerned that it would be too hard to set up.
Or maybe you were worried that it would be too complicated to back out of if you changed your mind.
Well, we’ve got good news for you: our new Cloudflare Integration feature makes both of these issues go away! Plus it has a nice security perk included.
Let’s take a look!
Ease of Setup
Anyone who is going to use QUIC.cloud CDN needs to make changes to their DNS to support it. (This is true for any CDN that protects your IP address, by the way. It’s not just a QUIC.cloud thing.)
Usually making DNS updates is a manual process, but with Cloudflare Integration, we can automate it all. Whether you find DNS intimidating, or you are a seasoned pro, wouldn’t it be nice to have someone else take care of the details?
When you sign up for QUIC.cloud CDN with Cloudflare Integration we handle all of this on your behalf:
- Back up your domain’s existing DNS settings
- Generate a wildcard SSL certificate for your domain
- Point your domain’s DNS to QUIC.cloud CDN
- Enable QUIC.cloud CDN for your domain
And if you ever want to add a domain alias, or make changes to your www and non-www settings, Cloudflare Integration will take care of the related DNS updates there, too. This is all possible via a Cloudflare API token.
No Risk
If you are not 100% in love with QUIC.cloud, we’ll be sorry to see you go. Nevertheless, we’ll put everything back exactly as it was before. Cloudflare Integration allows us to undo all of the DNS changes we made and restore your DNS to its pre-QUIC.cloud state.
No Gap in SSL Coverage
And now for the security perk I mentioned earlier: with Cloudflare Integration, we can generate your domain’s SSL certificate before pointing your DNS to QUIC.cloud. This means that your domain has SSL coverage the moment the CDN is enabled.
This is not possible for users who manually configure their CNAME DNS records for QUIC.cloud. Without Cloudflare Integration, there’s an up-to-20-minute gap between activating the CDN, and having a valid SSL certificate for the domain.
Conclusion
So, Cloudflare user, what do you say? Trying out QUIC.cloud is as easy as 123!
- Pair your WordPress site with QUIC.cloud
- Create a QUIC.cloud account
- Enable Cloudflare Integration
Cloudflare Integration is available to try right now, so be sure to see our documentation to learn how to get started.
Need more convincing? Over the next few weeks, we’ll be publishing a series of articles that explore the performance benefits of switching from Cloudflare to QUIC.cloud. Stay tuned!
Could there be a feature to integrate between ClouDNS and Quic.cloud in the future perhaps?
Because I love ClouDNS, in the asia region their dns is the best.
Thanks you.
Thank you for your suggestion. I’ve passed it along to the team!
Also, I should point out that even without a dedicated integration option, you can certainly still use ClouDNS with QUIC.cloud. As long as you choose the CNAME option, you can use any DNS provider you like.
Hello, again. Our team looked into this suggestion, but because ClouDNS `ALIAS` records, which are needed for root domains, do not support CDN services, it would not be a good candidate for integration. Sorry to have disappointing news, but like I mentioned earlier, you can still use ClouDNS `CNAME` with a subdomain for QUIC.cloud, if you want to. We just can’t develop an integration tool for it.
Hi ms. Lisa
Glad to hear that, thanks for taking the time to explain. ^_^
I prefer to use Quic.cloud DNS, because i think Alias better than cname.
You’re welcome!