Vendor-specific DNS records

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 Open external link added to your DNS provider.

Once you add these records to Cloudflare:

• Test the configuration Open external link
• Do not add other MX records other than those provided by Google.

​​ Google Workspace service URLs

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

​​ Google site verification

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

​​ Amazon

​​ Amazon Route53

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

​​ Amazon S3 bucket

Find the URL Open external link 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 Open external link .

​​ Amazon ELB configuration

Refer to  Amazon’s ELB help content Open external link for guidance on ELB configuration at Amazon, but generally you should:

Add a CNAME record to Cloudflare for the hostname you receive from AWS, for example:

​​ Microsoft

​​ Microsoft 365

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

​​ Microsoft Azure

Follow Microsoft’s instructions on  configuring Azure DNS settings Open external link .

Then, add Azure’s required records to Cloudflare DNS.

​​ Miscellaneous vendors

​​ Discourse

To use Discourse with Cloudflare, refer to Using Discourse with Cloudflare: Best Practices Open external link .

​​ Forward Email

To use Cloudflare with Forward Email, refer to Forward Email configuration with Cloudflare Open external link .

​​ ClickFunnels

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

• Adding a Cloudflare subdomain Open external link
• Adding a Cloudflare domain Open external link

​​ Zoho

To use Cloudflare with Zoho, refer to Zoho configuration with Cloudflare Open external link .

​​ Unbounce

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

​​ SendGrid

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

​​ WPEngine

For help configuring WPEngine sites, refer to:

• Configuring DNS with WPEngine Open external link
• Cloudflare best practices Open external link

​​ Ning custom domain

For help with Ning, refer to Use a custom domain with Ning Open external link .

​​ SmugMug

For help with SmugMug, refer to Use a custom domain with SmugMug Open external link .

​​ Mailchimp

For help with Mailchimp, refer to Use a custom domain with Mailchimp Open external link .

​​ Rackspace CloudFiles

Configure Rackspace CloudFiles via CNAME record. Consult the Rackspace documentation Open external link .

Refer to Rackspace CloudFiles’s documentation to get a CNAME value Open external link , then add that record within Cloudflare.

​​ Squarespace

First, make sure you update your nameservers and your domain is active.

Then, set up your Squarespace DNS records:

1. Get your Squarespace DNS information by following these instructions Open external link .
2. In Cloudflare, add those records:
   • All A records should be Proxied
   • The CNAME record for www should also be Proxied.
   • The CNAME record for verify.squarespace.com should be DNS-only.
3. If set up properly, your Squarespace DNS Settings page will now indicate that your ‘Settings contain problems.’ This is the expected behavior.

​​ Pending domain owner verification

The CNAME record you added for verify.squarespace.com should be DNS-only.

If you proxy this record, Squarespace will not be able to verify your domain ownership and show you a This website is pending domain owner verification error. To fix the issue, edit the CNAME record and change the Proxy status to DNS-only.

​​ Tumblr custom domain

Refer to Tumblr’s documentation to get DNS record values Open external link . Then, add records to Cloudflare DNS.

​​ Wix

You can use Cloudflare with Wix websites Open external link , though your setup needs to be different than with most website builders.

This is because Wix does not support Open external link using Cloudflare nameservers (which is the normal part of a full setup or with domains bought through Cloudflare Registrar).

​​ Using domain pointing

If you want to manage your DNS through Cloudflare or you bought a domain through Cloudflare Registrar, you can connect that domain to Wix through domain pointing Open external link .

This method means your website is using Cloudflare for DNS only, so all your DNS records should be DNS-only (unproxied).