Setting Up a Domain on Cloudflare: The DNS Pitfalls
Cloudflare's DNS dashboard looks like any other, with one extra control that changes what a record actually does: the proxy toggle. Getting it wrong on the right record is the single most common way a Cloudflare migration breaks something.
Orange Cloud vs. Grey Cloud
A grey-clouded record is plain DNS — Cloudflare answers the query, nothing more. A proxied (orange-clouded) record routes traffic to that hostname through Cloudflare's network first, which is what enables the CDN caching, DDoS protection and WAF Cloudflare is known for. Critically, proxying only ever applies to HTTP and HTTPS traffic — it has no effect on any other protocol.
Why Proxying Breaks Email
MX records themselves can't be proxied — Cloudflare's dashboard doesn't even offer the toggle for them. The actual trap is the A record an MX target depends on: if your MX record points to mail.yourdomain.com, and that hostname's own A record is orange-clouded, incoming mail servers try to deliver over SMTP to Cloudflare's proxy IP, which doesn't speak SMTP. That specific A record has to stay grey-clouded even if other records for similar-looking hostnames are proxied for web traffic.
SPF and Cloudflare Email Routing
Enabling Cloudflare's own Email Routing adds the MX and TXT records it needs automatically — adding your own conflicting entries for the same purpose afterward, rather than letting Cloudflare manage them, is a common way to end up with duplicate or contradictory SPF includes.
DNSSEC Is One Click, With a Manual Step After
Enabling DNSSEC in the Cloudflare dashboard is a single toggle, but it isn't complete until you take the DS record Cloudflare generates and add it at your domain's registrar. Skipped, this leaves DNSSEC in a half-enabled state that shows as an error rather than protection — enabling it and never finishing the registrar step is worse than not enabling it at all.
Check a Domain's Current DNS
See the theory in practice — run a DNS Lookup for your own domain.