There’s a lot of reasons to use CloudFlare. There’s many more reasons to use CDN.net. But did you know you can use them together?
First, why would you use both CDN.net and CloudFlare?
Using a CDN.net & CloudFlare combination offers many performance and security enhancements to a website. CDN.net offers high performance CDN, that typically outperforms CloudFlare’s free offering. As we’re a paid product, while CloudFlare is freemium, we can focus our efforts on ensuring our clients get a high cache hit rate (see more on that here), and ensure we have proper capacity at each of our 86 CDN PoPs.
Using CloudFlare’s free plan in conjunction adds a few additional benefits, like real time analytics, basic DDoS, and WAF protection, email address obfuscation, and always online caching, so if your hosting provider goes down, CloudFlare can show a cached backup. It’s the best of both worlds – high performance CDN from CDN.net & added security through CloudFlare.
To get started, you’ll need to have an account with both CDN.net & CloudFlare. If you’re using another CDN provider, you can still follow along and see the benefits, but you’ll have the best experience if you’re using CDN.net. You can signup to both using the links below.
Getting started using CloudFlare & CDN.net.
1.) First you’ll want to create a new resource in the CDN.net portal.
2.) Upon signup at CloudFlare, it will automatically recognize your existing DNS zones. You will want to make sure all appears correct before proceeding. If everything looks good, you’ll need
to create a new cname entry to your CloudFlare DNS zone. This cname entry will be the CDN hostname that you created in the CDN.net portal.
[Note: You will want to make sure the orange CloudFlare next to the DNS entry is not activated. When the cloud is orange, it is activated. In this case, we want it gray, otherwise you will not see all the performance benefits from CDN.net.]
3.) You’ll need to do some ‘advanced’ configuration of your CDN. service. Don’t worry, it’s super simple. First click on the advanced button under your CDN resource.
Next, just check the box set to ‘ignore set-cookie’ attribute. This will ensure that your static content is still delivered through CDN.net.
4.) There’s one final step! If you were not already using CloudFlare, you will need to change your DNS to point to CloudFlare’s DNS servers. CloudFlare will have given you the DNS servers at signup, however if not, you can retrieve them from the DNS section of the CloudFlare control panel.
Now you’re all set. You will need to setup your site to use CDN.net, however we’ve made that easy too. See our CDN integration guides for WordPress, Drupal and many other popular platforms in our knowledgebase.