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

Adding vendor-specific DNS records to Cloudflare

​​ Adding DNS records for vendors

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

Add the following MX records:

NameTTLRecord TypePriority Target

Once added, the DNS records appear similar to the following in Cloudflare’s DNS app:

Test the Google Apps email configuration.

Add a CNAME record for Google App Engine to Cloudflare DNS.

For example, if the domain is, the CNAME record is similar to:


To configure a redirect for a Google Apps domain, refer to  Google’s guide on URL forwarding.

​​ Amazon

AWS customers must update their domain’s nameservers to point to the Cloudflare nameservers listed in the Overview app of the Cloudflare dashboard:

  1. Log into AWS.
  2. Click My Account in the top-right of the navigation bar.
  3. Select AWS Management Console from the dropdown.
  4. Click Services and select Route 53.
  5. Update nameservers in two places:
  • Click Hosted zones and select the domain to update with Cloudflare’s nameservers.

  • Edit the nameservers to point to Cloudflare’s nameservers.

  • Click Registered domains.

  • Select the domain to update with Cloudflare’s nameservers.

  • Click Add or edit name servers.

Consult Amazon’s documentation on how to  create an Amazon S3 bucket.

Note the full host URL assigned to the bucket.

Add a CNAME record for the AWS bucket in Cloudflare DNS. For example, if the full host URL of the bucket is, add a CNAME record similar to the following:

files CNAME

Refer to Amazon’s documentation about  SES and verification settings.

Find the TXT and CNAME verification records that Amazon provides.

Add the records to Cloudflare DNS.  For example, if the Cloudflare domain is, the DNS records are similar to the following: TXT "fmxqxT/icOYx4aA/bEUrDPMeax9/s3frblS+niixmqk=" CNAME

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: is the proper CNAME target format (for example:
  3. Reach out to AWS support to determine AWS hostname or region.

​​ Microsoft

Follow Microsoft’s instructions on  configuring Azure DNS settings.

Add Azure’s required records to Cloudflare DNS.

For example, if the domain is, the record format is similar to: A CNAME

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

​​ Miscellaneous vendors

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:

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

  • Add Zoho MX records: MX (set Priority to 10) MX (set Priority to 20)
  • (Optional) Add an SPF record: TXT v=spf1 mx ~all
mail CNAME
zb******** CNAME

Typically, the DNS records are similar to the list below. Replace with the actual domain name:

email CNAME SPF v=spf1 a mx ~all TXT v=spf1 a mx ~all CNAME
smtpapi._domainkey.e.EXAMPLE.COM CNAME

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

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

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.

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

photo CNAME
photos CNAME

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.

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 is the Mandrill domain, add DNS records similar to the following. TXT v=spf1 ?all TXT v=DKIM1\; (values from Mandrill)

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

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 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.

If is the custom domain, add DNS records to Cloudflare similar to these below: A CNAME