Cloudflare Docs
Support
Support
Visit Support on GitHub
Set theme to dark (⇧+D)

Adding vendor-specific DNS records to Cloudflare

This article requires prior knowledge of DNS record management via the Cloudflare dashboard.  To learn more, refer to Cloudflare’s article on managing DNS records.

​​ Google

​​ Google Workspace MX records

Google Workspace requires specific MX records added to your DNS provider.

Once you add these records to Cloudflare:

​​ Google Workspace service URLs

If you want to customize the service addresses URLs associated with Google Workspace, refer to Google’s documentation.

​​ Google site verification

To add a site verification record in Cloudflare, follow Google’s documentation.


​​ Amazon

​​ Amazon Route53

AWS customers must update their domain’s nameservers to point to their new Cloudflare nameservers.

​​ Amazon S3 bucket

Find the URL for your bucket.

Then, create a CNAME record in Cloudflare. For example, if the full host URL of the bucket is files.example.com.s3.amazonaws.com, you would add a CNAME record similar to the following:

files CNAME files.example.com.s3.amazonaws.com

​​ Amazon Simple Email Service (SES)

For help setting up DKIM in SES, refer to the Amazon documentation.

​​ Amazon ELB configuration

Refer to  Amazon’s ELB help content for guidance on ELB configuration at Amazon.

  1. Add a CNAME record to Cloudflare for the hostname; for example: elb
  2. In the Cloudflare DNS app, replace Domain name with the ELB target: _.._elb.amazonaws.com is the proper CNAME target format (for example: _my-cool-cachepp-1344276401.eu-west-1._elb.amazonaws.com).
  3. Reach out to AWS support to determine AWS hostname or region.

​​ Microsoft

​​ Microsoft 365

For information about the records to Microsoft 365, refer to Microsoft’s documentation.

​​ Microsoft Azure

Follow Microsoft’s instructions on  configuring Azure DNS settings.

Add Azure’s required records to Cloudflare DNS.

For example, if the domain is example.com, the record format is similar to:

example.com A 192.0.1.2
www.example.com CNAME example.azurewebsites.net

For verification records, refer to Azure’s documentation on  creating domain verification records.


​​ Miscellaneous vendors

​​ ClickFunnels

You can configure Cloudflare to work with ClickFunnels. The process requires updating your Cloudflare DNS settings.

The following articles from ClickFunnels outline how to best configure the two services for your site:

​​ Zoho

Refer to the examples below for adding proper Zoho DNS records to Cloudflare. In all examples, replace example.com with the actual domain name:

  • Add Zoho MX records:
example.com MX mx.zohomail.com (set Priority to 10)
example.com MX mx2.zohomail.com (set Priority to 20)
  • (Optional) Add an SPF record:
example.com TXT v=spf1 mx include:zoho.com ~all
mail CNAME business.zoho.com
zb******** CNAME business.zoho.com

​​ Unbounce

Refer to Unbounce’s documentation to get a CNAME value, then add that record within Cloudflare.

​​ SendGrid

Refer to SendGrid’s documentation for how to make SendGrid compatible with Cloudflare.

​​ WPEngine

Consult WPEngine’s documentation on DNS configuration.

Determine whether to add an A or CNAME record to Cloudflare DNS: Finding your IP address at WPEngine.

​​ Ning custom domain

Refer to Ning’s documentation on  Custom Domains and DNS entries.

If the Ning custom domain is  www.example.com, add a CNAME and an A record as follows:

www.example.com CNAME example.ning.com.
example.ning.com A 208.82.16.68

After Ning verifies the domain, change the grey-cloud icon to an orange-cloud for the Ning DNS records so traffic can proxy to Cloudflare.

​​ SmugMug

Consult SmugMug documentation for the latest details on DNS record requirements. Typically, add CNAME records for SmugMug similar to the following:

photo CNAME domains.smugmug.com
photos CNAME domains.smugmug.com

After SmugMug verifies the domain, change the grey-cloud icon to an orange-cloud for the SmugMug DNS records so traffic can proxy to Cloudflare.

​​ Mandrill

Refer to  Mandrill’s article on DNS records for the latest details on DNS record requirements.

Mandrill requires addition of SPF and DKIM records. Obtain the DNS record values from Mandrill.

Add the SPF and DKIM records as TXT records in the Cloudflare DNS app.

For example, if example.com is the Mandrill domain, add DNS records similar to the following.

example.com TXT v=spf1 include:spf.mandrillapp.com ?all
mandrill._domainkey.example.com TXT v=DKIM1\; (values from Mandrill)

​​ Rackspace CloudFiles

Configure Rackspace CloudFiles via CNAME record. Consult the Rackspace documentation.

Confirm the correct CNAME target with Rackspace support.

An example CNAME record appears as follows:

rack CNAME e0978.r18.cf2.rackcdn.com

​​ Squarespace

After ensuring that your domain nameservers are set to Cloudflare, 

  1. Log in to the Cloudflare dashboard.
  2. Click the appropriate Cloudflare account for the domain where you will add records.
  3. Ensure the proper domain is selected.
  4. Click the DNS app.
  5. Ensure that all four (4) A records and the www CNAME from Squarespace are mark Proxied.
  6. Ensure that the verify.squarespace.com CNAME record is marked DNS Only.

If set up properly, your Squarespace DNS Settings page will now indicate that your ‘Settings contain problems.’ This is the expected behavior.

Screenshot of error warnings in squarespace

Now that your traffic is being sent through Cloudflare, Squarespace and your site’s visitors will see Cloudflare IP addresses. This causes Squarespace console to assume your site is misconfigured as Cloudflare IPs are returned instead of Squarespace assigned addresses. As long as you’ve configured Cloudflare DNS appropriately (above steps 1-6), your Squarespace site should now be working through Cloudflare.

​​ Tumblr custom domain

If example.com is the custom domain, add DNS records to Cloudflare similar to these below:

example.com A 66.6.44.4
www.example.com CNAME domains.tumblr.com