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 ↗ added to your DNS provider.

Once you add these records to Cloudflare:

• Test the configuration ↗
• 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 ↗.

Warning

Google enforces HTTPS on its services. If you find errors about redirect loops when browsing to your site through Cloudflare, use Cloudflare’s Full encryption mode.

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, but generally you should:

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

Type	Name	Target	Proxy status
CNAME	elb	<AWS_HOSTNAME>.<REGION>._elb.amazonaws.com	Proxied

Amazon Amplify

To use Cloudflare DNS with AWS Amplify, refer to the Amplify help content ↗ and follow the instructions for manual configuration.

At Cloudflare, you will need at least two CNAME records:

• A DNS-only CNAME to validate your domain ownership, which should look like the following:

Type	Name	Target	Proxy status
CNAME	<UNIQUE_STRING>	<UNIQUE_STRING>.mhbtsbpdnt.acm-validation.aws	DNS only

CNAME flattening

If your Cloudflare zone is on a paid plan, also make sure that the Flatten option turned off for the validation CNAME record, and that you zone is not using CNAME flattening for all CNAME records.

• One CNAME for the apex domain (example.com) and/or for each of the subdomains (blog.example.com) that you want to manage on Cloudflare. For details refer to Manage DNS records. These records can be proxied.

Type	Name	Target
CNAME	@	<AMPLIFY_HOSTNAME>.cloudfront.net

Type	Name	Target
CNAME	blog	<AMPLIFY_HOSTNAME>.cloudfront.net

---

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

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

---

Miscellaneous vendors

ClickFunnels

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

• Adding a Cloudflare subdomain ↗
• Adding a Cloudflare domain ↗

Discourse

To use Discourse with Cloudflare, refer to Using Discourse with Cloudflare: Best Practices ↗.

Forward Email

To use Cloudflare with Forward Email, refer to Forward Email configuration with Cloudflare ↗.

Mailchimp

For help with Mailchimp, refer to Use a custom domain with Mailchimp ↗.

Note

When you add records to Cloudflare DNS, those records should be DNS-only (unproxied) until Mailchimp verifies your domain. Then, you can switch your DNS records to Proxied.

Ning custom domain

For help with Ning, refer to Use a custom domain with Ning ↗.

Note

When you add records to Cloudflare DNS, those records should be DNS-only (unproxied) until Ning verifies your domain. Then, you can switch your DNS records to Proxied.

Rackspace CloudFiles

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

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

Warning

The CNAME record needs to be DNS-only (unproxied) since rackcdn.com is not compatible with Cloudflare.

SendGrid

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

Note

You may need to refer to Cloudflare’s documentation for updated navigation instructions regarding adding DNS records and creating Configuration rules.

SmugMug

For help with SmugMug, refer to Use a custom domain with SmugMug ↗.

Note

When you add records to Cloudflare DNS, those records should be DNS-only (unproxied) until SmugMug verifies your domain. Then, you can switch your DNS records to Proxied.

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 ↗.
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 ↗. Then, add records to Cloudflare DNS.

Note

When you add records to Cloudflare DNS, those records should be DNS-only (unproxied) until Tumblr verifies your domain. Then, you can switch your DNS records to Proxied.

Unbounce

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

Warning

If Cloudflare is activated via one of our hosting partners, your CNAME record should be DNS-only (unproxied).

Vercel

For help using Cloudflare with Vercel, refer to Vercel and Cloudflare Integration ↗

Wix

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

This is because Wix does not support ↗ 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 ↗.

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

WPEngine

For help configuring WPEngine sites, refer to:

• Configuring DNS with WPEngine ↗
• Cloudflare best practices ↗

Zoho

To use Cloudflare with Zoho, refer to Zoho configuration with Cloudflare ↗.