| Type | Name | Target | Proxy status |
|---|---|---|---|
CNAME | elb | <AWS_HOSTNAME>.<REGION>._elb.amazonaws.com | Proxied |
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 Workspace requires specific MX records ↗ added to your DNS provider.
Once you add these records to Cloudflare:
- Test the configuration ↗
- Do not add other
MXrecords other than those provided by Google.
If you want to customize the service addresses URLs associated with Google Workspace, refer to Google's documentation ↗.
To add a site verification record in Cloudflare, follow Google's documentation ↗.
AWS customers must update their domain's nameservers ↗ to point to their new Cloudflare nameservers.
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.comFor help setting up DKIM in SES, refer to the Amazon documentation ↗.
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:
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
CNAMEto 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 |
- One
CNAMEfor 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 |
For information about the records to Microsoft 365, refer to Microsoft's documentation ↗.
Follow Microsoft's instructions on configuring Azure DNS settings ↗.
Then, add Azure's required records to Cloudflare DNS.
You can configure Cloudflare to work with ClickFunnels. The process requires updating your Cloudflare DNS settings.
To use Discourse with Cloudflare, refer to Using Discourse with Cloudflare: Best Practices ↗.
To use Cloudflare with Forward Email, refer to Forward Email configuration with Cloudflare ↗.
For help with Mailchimp, refer to Use a custom domain with Mailchimp ↗.
For help with Ning, refer to Use a custom domain with Ning ↗.
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.
Refer to SendGrid's documentation for how to make SendGrid compatible with Cloudflare ↗.
For help with SmugMug, refer to Use a custom domain with SmugMug ↗.
First, make sure you update your nameservers and your domain is active.
Then, set up your Squarespace DNS records:
- Get your Squarespace DNS information by following these instructions ↗.
- In Cloudflare, add those records:
- All
Arecords should be Proxied - The
CNAMErecord forwwwshould also be Proxied. - The
CNAMErecord forverify.squarespace.comshould be DNS-only.
- All
- If set up properly, your Squarespace DNS Settings page will now indicate that your 'Settings contain problems.' This is the expected behavior.
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.
Refer to Tumblr's documentation to get DNS record values ↗. Then, add records to Cloudflare DNS.
Refer to Unbounce's documentation to get a CNAME value ↗, then add that record within Cloudflare.
For help using Cloudflare with Vercel, refer to Vercel and Cloudflare Integration ↗
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).
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).
For help configuring WPEngine sites, refer to:
To use Cloudflare with Zoho, refer to Zoho configuration with Cloudflare ↗.