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 

Google Apps mail

Add the following MX records:

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

Review the latest MX records required by Google App.

Test the Google Apps email configuration.

To avoid unexpected behavior, don’t use MX records other than Google’s.

Google App Engine

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

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

www  CNAME  ghs.googlehosted.com

Confirm the CNAME record value that Google requires for the domain.

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

Google enforces HTTPS on its services. If you are see errors about redirect loops when browsing to your site through Cloudflare, ensure that SSL is set to Full in the Crypto app of the Cloudflare dashboard.

Google site verification

Follow Google’s instructions for adding a site verification record to Cloudflare.

Amazon

AWS nameserver updates

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.

Amazon S3

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 files.example.com, add a CNAME record similar to the following:

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

Amazon requires that the CNAME match the bucket name as in the above example.

Amazon Simple Email Service (SES)

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 example.com, the DNS records are similar to the following:

example.com  TXT  "fmxqxT/icOYx4aA/bEUrDPMeax9/s3frblS+niixmqk=" verificationstring._domainkey.example.com  CNAME  verificationstring.dkim.amazonses.com

The above TXT record content is an example. Use the correct content provided by Amazon SES.

Amazon ELB (Elastic Load Balancing)

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

Cloudflare’s CNAME Flattening feature enables a CNAME record on the root domain to point to an Elastic Load Balancer.

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 Office 365, Lync, or Exchange Online

Refer to the documentation on Microsoft Office DNS setup for current details.

Additionally, refer to Cloudflare’s documentation on managing DNS records.

Add the DNS records that Microsoft utilizes for domain validation (such as autodiscover) with a grey-cloud icon.

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  203.0.113.1
www.example.com  CNAME  example.azurewebsites.net

Replace 203.0.113.1 with the actual IP address of the Azure site.

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

Add DNS records for Azure verification with a grey-cloud icon.

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:

• Adding a Cloudflare subdomain
• Cloudflare CNAME record

Zoho

Reference Zoho’s MX documentation and SPF documentation before adding DNS records to Cloudflare.

See 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

• (Optional) To access mail through a custom Zoho URL, add a CNAME record:

mail  CNAME  business.zoho.com

• (Optional) To add a Zoho domain validation record:

zb******** CNAME  business.zoho.com

The zb record is unique for each domain. Add the unique zb verification code provided by Zoho.

Unbounce

Refer to Unbounce’s documentation to determine the CNAME record to add to Cloudflare.

Add the CNAME record with a grey-cloud icon if Cloudflare is activate via one of our hosting partners.

SendGrid

Confirm what records SendGrid requires to set in Cloudflare’s DNS.

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

email  CNAME  sendgrid.net
example.com  SPF  v=spf1 a mx include:sendgrid.net ~all
example.com  TXT  v=spf1 a mx include:sendgrid.net ~all mtpapi._domainkey.EXAMPLE.com  CNAME  dkim.sendgrid.net. smtpapi._domainkey.e.EXAMPLE.COM  CNAME  dkim.sendgrid.net

Add DNS records with a grey-cloud icon. SendGrid cannot verify a mail configuration when Cloudflare’s proxy is enable.

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 WP engine
• Consult Cloudflare’s documentation on Managing DNS records for details on adding the records.

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

Add the DNS records to Cloudflare with a grey-cloud icon until Ning verifies the domain.

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

Add the DNS records to Cloudflare with a grey-cloud icon until SmugMug verifies the domain.

After SmugMug verifies the domain, it will 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, then 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 CloudFiles documentation.

Confirm the correct CNAME target with Rackspace support.

An example CNAME record appears as follows:

rack  CNAME  e0978.r18.cf2.rackcdn.com

Therefore, CNAME record cannot be proxied to Cloudflare since rackcdn.com is not compatible with Cloudflare.

Tumblr custom domain

Tumblr’s systems are not compatible with Cloudflare’s proxy services and Tumblr customers cannot use Cloudflare’s SSL services.

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

Disable Cloudflare’s proxying for any DNS record related to Tumblr. Otherwise, Tumblr’s custom domain verifications will fail.