How to Setup Domain on Cloudflare
Step-by-step guide to configure DNS records on Cloudflare for Aurora SendCloud. Learn to set up SPF, DKIM, MX, and DMARC records for optimal email delivery.
This guide walks you through adding a primary domain or subdomain in Cloudflare and configuring the DNS records that Aurora SendCloud requires.
Prerequisites:
- Create a Cloudflare account at cloudflare.com if you don't already have one.
- Add your domain or subdomain to your Aurora SendCloud account so the system generates the required DNS records.
If you encounter errors while configuring DNS records in Cloudflare, contact Cloudflare's support team directly—they can identify and resolve DNS-related issues most quickly.
Choosing a Primary Domain or Subdomain
Before proceeding, decide whether to use your primary domain or a subdomain. We recommend reviewing the following Aurora SendCloud article for guidance:
How to choose a sending domain
Here's a quick overview of the two options:
- Primary domains — for example,
aurorasendcloud.com,mydnsexample.com, orgoogle.com. - Subdomains — for example,
relay.aurorasendcloud.com,sc.mydnsexample.com, ormail.google.com. Subdomains have an additional prefix before the primary domain.
In most cases, using a subdomain with Aurora SendCloud is the preferred option.
Adding a Domain
There are several ways to add a domain or subdomain to Cloudflare:
Method 1: Register a new domain or subdomain with Cloudflare.
Method 2: Transfer an existing domain or subdomain registration from another registrar to Cloudflare.
Method 3: Update the name servers of your existing domain at your registrar to point to Cloudflare instead of your current DNS provider.
This guide will focus on the first and third methods.
Registering a New Domain (Method 1)
If you need to create a new domain or subdomain and have it hosted on Cloudflare, follow these steps:
- Log in to your Cloudflare account.
- Click Domain Management (or a similar option).
- Click Add Domain.
- Enter the new domain you want to register.
- Follow the prompts to complete the registration process.
Using an Existing Domain (Method 3)
If you already have an existing domain or subdomain registered elsewhere but would like to manage your DNS with Cloudflare, follow these steps:
- Log in to your Cloudflare account.
- Add your existing domain to Cloudflare's DNS management.
- Note the NS (name server) records that Cloudflare displays—you'll need these in the next step.
- Update the name server records at your domain registrar to the values provided by Cloudflare.
Configuring the Domain
Once the domain has been added, you can access it by following these steps:
- Log in to your Cloudflare account.
- Go to Domain Management.
- Find the domain you want to configure and click Manage.
- Click Add Record to begin configuring DNS records.
Configuring SPF
SPF (Sender Policy Framework) records help protect your domain from email spoofing and reduce the likelihood that your emails are marked as spam.
Configuring an SPF Record for a Primary Domain
In your Cloudflare dashboard, enter the SPF record information displayed in the Aurora SendCloud dashboard.
| Field | Value |
|---|---|
| Record Type | TXT |
| Host Record | @ |
| Record Value | v=spf1 include:sendcloud.org ~all (When activating multiple regions, please configure according to the actual requirements on the page) |
| TTL | 600 (seconds) |
If you already have an SPF record for this primary domain, insert
include:sendcloud.orginto the existing record. Place this text afterv=spf1and before~all.
Configuring SPF Records for Subdomains
| Field | Value |
|---|---|
| Record Type | TXT |
| Host Record | Subdomain Prefix (e.g., sc) |
| Record Value | v=spf1 include:sendcloud.org ~all (When activating multiple regions, please configure according to the actual requirements on the page) |
| TTL | 600 (seconds) |
Configuring DKIM
DKIM (DomainKeys Identified Mail) records verify your domain's identity to prevent forged emails and reduce the likelihood of your emails being marked as spam.
Configuring a DKIM Record for a Primary Domain
| Field | Value |
|---|---|
| Record Type | TXT |
| Host Record | sendcloud._domainkey (or the value assigned by Aurora SendCloud for your domain) |
| Record Value | k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUA... (Please configure according to the actual requirements on the page) |
| TTL | 600 seconds |
Your DKIM host record may have a different value, such as
default._domainkeyorsc._domainkey. Always use the value assigned by Aurora SendCloud for your domain.
Configuring a DKIM Record for a Subdomain
| Field | Value |
|---|---|
| Record Type | TXT |
| Host Record | sendcloud._domainkey.subdomain prefix (e.g., sendcloud._domainkey.sc) |
| Record Value | k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUA... (Please configure as specified on the page) |
| TTL | 600 (seconds) |
Configuring MX Records
MX (Mail Exchange) records specify where emails sent to your domain should be delivered.
Configuring an MX Record for the Primary Domain
| Field | Value |
|---|---|
| Record Type | MX |
| Host Record | @ |
| Record Value | mx.sendcloud.org (Please configure as specified on the page when enabling multiple regions) |
| Priority | 10 |
| TTL | 600 (seconds) |
Ensure that only Aurora SendCloud MX records are configured for your domain. Existing MX records from other email providers can cause unpredictable email delivery.
Configuring MX Records for a Subdomain
| Field | Value |
|---|---|
| Record Type | MX |
| Host Record | Subdomain Prefix (e.g., sc) |
| Record Value | mx.sendcloud.org (When enabling multiple regions, please configure according to the instructions on the page) |
| Priority | 10 |
| TTL | 600 (seconds) |
Configuring DMARC
DMARC (Domain-based Message Authentication, Reporting & Conformance) is an email authentication protocol that protects your domain from spoofing and phishing attacks. It builds on SPF and DKIM to provide policy guidance for inbox providers.
Configuring a DMARC Record for the Primary Domain
| Field | Value |
|---|---|
| Record Type | TXT |
| Host Record | _dmarc |
| Record Value | v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1 |
| TTL | 600 seconds |
Parameter Descriptions:
v=DMARC1: Protocol versionp=none: Monitor mode (no enforcement)p=quarantine: Quarantine mode (messages that fail verification will be sent to spam)p=reject: Reject mode (messages that fail verification will be rejected)rua: Email address for aggregated reportsruf: Email address for forensic reportsfo=1: Generate a failure report if any authentication check fails
Configuring a DMARC Record for a Subdomain
| Field | Value |
|---|---|
| Record Type | TXT |
| Host Record | _dmarc.Subdomain prefix (e.g., _dmarc.sc) |
| Record Value | v=DMARC1; p=none; rua=mailto:[email protected] |
| TTL | 600 seconds |
Domain Registrar and Name Server Records
If you recently migrated from another DNS hosting provider (or are currently migrating) and your Aurora SendCloud DNS records fail to verify, you may need to update your domain's name server records.
When switching DNS hosting providers, you must update the NS (name server) records at your registrar—the company where you purchased and registered your domain name.
If you need help identifying your domain's registrar, the ICANN WHOIS website can assist with this task.
Need Support?
Contact the Aurora SendCloud support team from the Support page in your Aurora SendCloud control panel.
Important Notes
- The DNS record values in this guide are examples only. Refer to the actual values displayed in your Aurora SendCloud dashboard.
- After configuration, DNS records may take several minutes to several hours to propagate globally.
- Set the TTL to a low value (300–600 seconds) for faster verification. After successful verification, you can increase it as needed.
Updated about 3 hours ago
