> ## Documentation Index
> Fetch the complete documentation index at: https://gcore.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrate CDN resource with Cloudflare

## CNAME record setup

If you use the Cloudflare DNS service, the Cloudflare servers function as proxy for all DNS records. The Cloudflare's DDoS protection and CDN services are based on that.

If you want to use Gcore as your CDN provider, disable the proxying in the Cloudflare DNS settings by clicking the cloud icon during the [CNAME record creation](/cdn/cdn-resource-options/general/create-and-set-a-custom-domain-for-the-content-delivery-via-cdn).

<Frame>
  <img src="https://mintcdn.com/gcore/dxycBbQXMfI-sCbi/images/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-clouldflare/1574936519330.png?fit=max&auto=format&n=dxycBbQXMfI-sCbi&q=85&s=0ae03299bdd0d62fe7e59fd2884ed10a" alt="CNAME record setup" width="1876" height="255" data-path="images/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-clouldflare/1574936519330.png" />
</Frame>

## Origin pull protocol setup

Due to the differences in our and Cloudflare's infrastructures, if you set HTTPS as your "Origin Pull Protocol", you will likely start getting 502 errors.

To avoid it, add the [Change SNI Hostname](/cdn/cdn-resource-options/security/set-the-hostname-passed-in-sni-requests-to-the-origin-server) option in the "Security" section or change "Origin Pull Protocol" to HTTP.