Cloudflare integrated with other CDN

I wish to use for now my BunnyCDN integrated with Cloudflare. I already change DNS in Namecheap. When I get in the DNS section, I see all the cnames that I had set up in Namecheap, including the cname to BunnyCDN. What I have to change?

I’m in the same boat and get mixed messages.
I use Cloudflare since I moved my DNS over a while back and I just started using MaxCDN through my hosts plan (since it’s included with hosting). Is there any features I should disable now with Cloudflares free account or use it same as always? My end goal is speed and it would be great to be able to have speed with Cloudflare security. it’s just that I can’t get a satisfying answer to this question.

Do you guys have any examples of your websites working with other CDN services? It’s not generally a problem combining Cloudflare with other CDN services, and it doesn’t require any specific configuration.

Depending on how your CDN is setup, it might be serving assets directly from the CDN without passing through Cloudflare (which is entirely fine for a CDN delivering static files). Or you might be getting an “accumulative” CDN effect where your assets are cached on both 3rd party CDN service AND Cloudflare CDN (chained through requests), and although that’s cool, it’s unlikely this will serve much purpose.

hi josh15 and imagevuex,

Glad that you are here!

josh15: There is difference, between as because I had chosen to have a CDN, and I setup the cname in Namecheap.

imagevuex: What I have done in DNS Cloudflare section, is click in the gray cloud for the cname that delivers the static content from BunnyCDN. And the pages go through the orange cloud. I think that in this way I avoid the static image been delivered by Cloudflare.

I have a cuple of more questions:

  1. Now my images are delivered in the following way:

In case I deliver static and dynamic content, both from cloudflare.

I will return to the following?

  1. Is there is a Bandwidth Usage limit for free account?

  2. The Pro plan is a flat rate for one site, no matter your bandwidth usage is?

  3. Did you install the Cloudflare wp plugin?

  4. Did you setup the page rules for wp?

Thanks for sharing!

1 Like

That is right. However, even if you ENABLE the orange cloud, everything on that CNAME would still be delivered from BunnyCDN. The difference is that you will have two layers of CDN, with Cloudflare CDN in front of BunnyCDN. There may be some advantages to this, but likely minimal.

Not 100% sure I understand the question, but if you have setup to point to BunnyCDN, then everything requested from* will be requested from BunnyCDN (and with orange cloud OFF, the request will entirely bypass Cloudflare). Everything else on, will go through Cloudflare, whereas some requests (static assets like images, js, css etc) will get cached (on Cloudflare CDN), while other requests (html) will not get cached (but still served through Cloudflare).

Nothing wrong with this combination!



No. I believe it’s mostly shortcuts to Cloudflare features that you already have available in the Cloudflare dashboard, but directly from your wp-admin.

Not specifically for WP no. I don’t see any WP-specific page rules you would need to create. The only thing I would personally do with a WP website, is add Cloudflare ACCESS to the wp-login.php URL. So many bots attempting to hack WP websites.


Thanks for your answer.

I was thinking in what you said, that wasn’t wrong to have static content passing through both CDN, so I enabled again. Besides the security services that Cloudways offers, also has servers in my country, and BunnyCDN not. Being most of the users from my country, this can make a difference in lattency time. So, thanks for your comment.

With reference to access, by now I am the only user with login capabilities, so I setup two firewall rules, to block any other IP trying to login. I expected this works because sense Cloudflare integration I had to disable Wordfence plugin, that is causing an issue in login.

Thanks for every thing

This topic was automatically closed after 31 days. New replies are no longer allowed.