What this means
What this means
Cloudflare can improve DNS management and security, but incorrect records can break websites, email, SSL, or app routing.
Before you start
Before you start
Prepare the domain, zone ownership, current DNS records, email records, target service, and rollback expectation.
Step-by-step guidance
Step-by-step guidance
- List existing A, CNAME, MX, TXT, and verification records.
- Confirm which records are website/app records and which support email.
- Preview DNS changes before applying them.
- Change one approved record at a time when possible.
- Verify website, SSL, and email after any DNS change.
What CM Cloud support will review
What CM Cloud support will review
Support reviews zone ownership, allowed records, DNS change preview, rollback plan, and whether a mutation capability is enabled.
What is not automated yet
What is not automated yet
This guide does not connect Cloudflare, mutate DNS, delete records, change nameservers, or call providers.
Safety note
Safety note
Reading this article does not capture payment, provision infrastructure, register or transfer domains, change DNS, write Cloudflare or WHMCS, call providers, start workers, create retries, or enable live execution.
Safe next action
Safe next action
Use the Domains page for read-only DNS visibility or ask support before a production DNS change.