At Cloudflare, records are under DNS → Records. You type the name without your domain, @ for the domain itself — and every A, AAAA and CNAME record has a proxy switch that must be off (DNS only) for DKIM keys, verification records and anything mail-related.
| Name field | Without the domain; @ for the root |
| Proxy | A, AAAA, CNAME only — DNS only for mail and verification |
| Long TXT values | Split into 255-character strings for you |
| Alias at the root | CNAME flattening, on every plan |
| TTL | Auto = 300 seconds; 60 seconds minimum |
| Nameservers | two names under ns.cloudflare.com |
Where the DNS records are
In the Cloudflare dashboard, choose the domain, then DNS → Records → Add record. DNSSEC is under DNS → Settings.
What to type in the name field
Cloudflare adds your domain to the name: type _dmarc, not _dmarc.example.com, and @ for the domain itself. (The API is the exception — it takes the complete name.)
| You were given a record for | Type in the name field |
|---|---|
| The domain itself — SPF, verification codes, MX | @ |
| DMARC | _dmarc |
| A DKIM key (selector s1, for example) | s1._domainkey |
| A subdomain such as www or mail | www |
Adding a record
- Choose the domain, then DNS → Records → Add record.
- Choose the type and enter the name as in the table above.
- Paste the value (quotes around a TXT value are optional — Cloudflare adds them).
- For a CNAME or A record that is a DKIM key, a verification record or anything mail uses, set Proxy status to DNS only (grey cloud).
- Leave TTL on Auto, and Save.
Check the record you just added
Enter the full name — _dmarc.yourdomain.com, s1._domainkey.yourdomain.com — and the type. If it answers, it is published; if it is not there yet, try again after a few minutes.
TXT records and long DKIM keys
Paste a long value — a 2048-bit DKIM key — in one piece: Cloudflare splits anything over 255 characters into several strings for you, which is why it is later shown as “part1” “part2”. A single TXT record can hold up to 4,096 bytes.
Pointing the root domain at a service
A CNAME at the root is allowed: Cloudflare flattens it, answering with the target’s addresses, on every plan. “Flatten all CNAMEs” (paid plans) flattens every CNAME, which can break verification records that must stay CNAMEs — leave it off unless you need it.
DNSSEC
Select Enable DNSSEC under DNS → Settings and Cloudflare shows the DS record. If the domain is registered elsewhere, add that DS record at your registrar; Cloudflare Registrar adds it for you. Before moving the domain’s nameservers to or from Cloudflare, turn DNSSEC off at the registrar first.
Common mistakes
- A DKIM or verification CNAME left Proxied (orange cloud): the answer becomes Cloudflare’s addresses and the check fails.
- The A record an MX points to left Proxied — mail servers cannot reach it.
- Turning on Flatten all CNAMEs and breaking a verification record.
- Changing nameservers while DNSSEC is still on at the registrar.
Setting up email? The exact records for each service are in our email setup guides; to watch a change reach resolvers worldwide, use the propagation checker.
Questions
How long do Cloudflare DNS changes take?
Cloudflare says changes reach its whole network within five minutes, usually less. Resolvers that cached the previous record keep it until its TTL runs out.
Should my DKIM CNAME be proxied?
No. Set it to DNS only. A proxied record answers with Cloudflare’s own addresses, so the mail service cannot find its key.
Sources
Checked against Cloudflare’s own documentation on 25 September 2026:
- Manage DNS records — developers.cloudflare.com
- Proxy status — developers.cloudflare.com
- CNAME flattening — developers.cloudflare.com
- DNSSEC — developers.cloudflare.com
- Time to Live (TTL) — developers.cloudflare.com