Quick Answer
To move a cPanel-hosted domain’s authoritative DNS to Cloudflare, preserve the complete active DNS zone, recreate and verify its required records in Cloudflare, handle the old DNSSEC delegation, then change the nameservers at the registrar. Keep website and service records DNS-only during that first change. Hosting, registration and email can remain with their existing providers when their records and server settings are preserved.
A DNS migration changes who answers the domain’s DNS questions. It does not copy website files, move mailboxes or transfer domain registration. Separating those jobs makes the migration easier to verify and gives you a more useful rollback plan.
If your storefront runs on Shopify, use our Shopify DNS and optional O2O guide for its platform-specific connection, proxy and certificate requirements.
1. Confirm the current authority and preserve the zone
Identify the registrar, current authoritative nameservers, web host and mail provider. These may be four different services. Check the public delegation instead of assuming that the DNS records visible in cPanel control the domain.
The cPanel Zone Editor manages records on that hosting system. If another provider is authoritative, obtain the active zone from that provider as well. A local cPanel zone can still matter to server operations even when it no longer supplies public DNS.
Before changing anything, save an export or complete record inventory, the registrar’s existing nameservers and the current DNSSEC details. Include names, types, values, priorities and TTLs. Preserve the website and database recovery copy separately; a DNS export cannot restore deleted site files or mailboxes.
Use a change window with access to the registrar, Cloudflare, hosting support and email administration. Assign someone to maintain both zones during the transition. Keep the previous DNS service available while cached delegation and record answers expire.
2. Add the domain and reconcile every required record
Add the exact apex domain, such as example.com, to the intended Cloudflare account. Cloudflare’s primary-zone setup guide covers onboarding, record review and registrar delegation. Check account ownership and access before continuing.
Compare the proposed zone with your saved inventory. Cloudflare’s quick scan documentation explains that uncommon names and custom DKIM selectors can be missed. A successful scan is a starting list, not proof that every service has been preserved.
| Record group | What to preserve or confirm |
|---|---|
| Website A, AAAA and CNAME | The host-confirmed destination for the apex, www and each real website subdomain. Investigate stale IPv6 records instead of inventing a replacement. |
| Mail delivery | Exact MX targets and priorities, plus the address records required by those targets. |
| Email authentication | Complete SPF, DKIM and DMARC values, including every active sender and selector. |
| Other services | Verification TXT or CNAME records, SRV entries, CAA policy, wildcard behavior and application-specific subdomains. |
| Delegated subdomains | Any intentional child-zone delegation and its required supporting records, reviewed with the DNS owner. |
Do not import the previous provider’s apex SOA and authoritative NS entries as ordinary replacements for Cloudflare’s own zone authority. Keep a deliberate child-subdomain delegation distinct from the apex delegation you are changing at the registrar.
Set applicable A, AAAA and CNAME records to DNS only for the migration baseline. Cloudflare may initially propose proxying web records, so inspect the status explicitly. Its proxy-status documentation distinguishes authoritative DNS from HTTP proxying; MX and TXT records themselves are always DNS-only.
If you import a zone file, review Cloudflare’s import settings as well. Unselect the general proxy option and inspect every applicable record afterward. An embedded cf-proxied tag can override that general setting.
3. Preserve email and check cPanel Email Routing
If the cPanel server hosts the mailboxes, preserve the actual mail-host address and MX destination. If an external provider handles email, retain that provider’s exact records. Moving DNS does not require replacing a working provider configuration with a generic mail example.
Keep hostnames used for SMTP, IMAP, POP, FTP and SSH DNS-only in this ordinary setup. Do not proxy a mail target merely because it is an A record. Cloudflare’s email troubleshooting guide explains that the standard HTTP proxy does not carry SMTP, IMAP or POP3. The MX target must resolve appropriately too.
A mail hostname that aliases a newly proxied website name needs particular attention. Ask the provider to confirm an appropriate direct mail destination before changing that relationship. Preserve autodiscover and verification CNAME behavior rather than applying flattening indiscriminately.
Check cPanel → Email Routing against the actual mail location. Local delivery, remote delivery and backup delivery have different meanings. Do not tell every account to select Local Mail Exchanger.
The cPanel Email Routing documentation states that automatic detection reads the local zone file, not a live lookup of Cloudflare’s authoritative zone. It also does not automatically revise the setting after later changes. Have the hosting provider verify the intended routing when public DNS is managed elsewhere.
For cPanel-originated mail, review its Email Deliverability information and publish approved public DNS values at the authoritative provider. A local Repair action cannot be assumed to update Cloudflare. Never publish a DKIM private key. Our SPF, DKIM and DMARC guide explains the separate authentication checks. The cPanel and Cloudflare email authentication walkthrough covers record publication and received-message verification in more detail.
4. Handle DNSSEC before changing registrar nameservers
For an ordinary migration, follow the registrar and current provider’s supported process to remove the old DNSSEC delegation safely. The parent-zone DS record connects the domain to its existing signing keys. Leaving an incompatible DS in place when nameservers change can make validating resolvers reject the new answers.
Check that the old DS has actually been removed from the parent authority and allow its cached lifetime to expire before proceeding. A registrar toggle or a query to the domain’s own nameserver is not the same evidence. Cloudflare’s migration planning guidance calls out the parent-zone DS TTL as a planning input. Have a DNS administrator handle a specialized migration that keeps DNSSEC active throughout.
Then update the registrar’s nameserver delegation to the exact pair assigned to this Cloudflare zone. Editing NS records inside cPanel does not change the registrar’s delegation. Do not mix one old nameserver with one new nameserver as a transition strategy.
Keep a timestamped record of the registrar change and Cloudflare’s activation status. Different resolvers can retain different cached answers. There is no single propagation deadline that proves every service is working.
5. Validate authority and the DNS-only baseline
Check delegation and records independently of the dashboard. If dig is available, these are illustrative read-only queries using the reserved example domain:
dig +trace example.com NS
dig +trace example.com DS
dig example.com A +short
dig example.com AAAA +short
dig example.com MX +short
dig example.com TXT +short
Read the trace at the relevant authority. For example.com, the parent is .com; other domain structures have different parents. A recursive answer can still be cached. Check the Cloudflare-assigned authorities directly when investigating a mismatch, and compare the actual record values with the inventory.
Confirm the apex and www destinations, HTTPS certificates, important subdomains and any primary-domain redirects. Test the contact form through to its real destination with authorized test details. A thank-you message alone does not prove delivery.
For email, test inbound mail from an independent provider and outbound mail to one. Check replies, any website-generated messages and the relevant authentication results. Record actual failures and bounce messages; a valid-looking MX record does not test mailbox delivery.
After the migration is healthy, enable Cloudflare DNSSEC where appropriate using the new DS values Cloudflare supplies and the registrar’s supported procedure. Verify the resulting chain. Do not reuse the old provider’s DS values.
6. Add an optional web proxy as a separate change
DNS-only operation is a useful completed baseline. If you want Cloudflare to proxy suitable website hostnames, plan that separately. Confirm host compatibility, origin reachability, certificates, redirects and the existing cache or firewall configuration first.
Keep end-to-end HTTPS. Cloudflare’s Full (strict) mode validates the origin certificate, including its hostname and validity. Prepare a valid origin certificate rather than choosing Flexible to work around an HTTPS problem.
Preserve a browser-trusted origin certificate if DNS-only fallback must remain usable. Cloudflare explains that Origin CA certificates are intended for the Cloudflare-to-origin connection and can produce browser trust errors when proxying is removed.
Check the host’s certificate-renewal method too. cPanel documents a Let’s Encrypt AutoSSL failure caused by blocked HTTP validation. Confirm that the actual validation requests can reach the required path, such as /.well-known/acme-challenge/, without an interfering challenge. Review any narrowly needed exception with the host; do not disable all protection as a permanent blanket solution.
7. Troubleshoot and choose the right rollback
- The site works but email fails
-
Compare MX targets, their address records and proxy status. Check cPanel’s local-versus-remote routing and the actual mailbox provider. Keep Cloudflare Email Routing separate from an existing mail-hosting service.
- Some resolvers fail after delegation
-
Check parent NS and DS evidence, cached answers and both zones. A DNSSEC mismatch needs a chain-of-trust correction, not random A-record edits.
- HTTPS fails only after proxying
-
Review the origin certificate, TLS mode, connectivity and redirects. Compare with the previously verified DNS-only baseline.
- A record is wrong
-
Restore the exact saved value in the active authoritative zone and verify it. This is usually a smaller change than moving nameservers again.
For a proxy-related failure, restore the saved DNS-only status and disable only the new related rules, after confirming direct HTTPS still works. Healthy Cloudflare authoritative DNS can remain.
For a delegation-level failure that requires returning to the old provider, first verify that the old zone is complete and available. Restore the saved nameservers at the registrar and coordinate DNSSEC so the parent DS matches the provider that will answer. Nameserver rollback also has cache delay; it is not an instant undo.
Our cPanel hosting describes the available hosting service, and website care plans cover ongoing website care. For help planning the change, contact Interactive Online with the current providers and the services the domain needs to preserve.
Key Takeaways
- Export and reconcile the active authoritative zone before changing delegation.
- Preserve hosting, email and service destinations, with DNS-only records at the migration baseline.
- Check cPanel Email Routing separately from public Cloudflare DNS.
- Handle old and new DNSSEC delegation in the correct sequence.
- Separate record repairs, proxy rollback and nameserver rollback.
Frequently Asked Questions
Does moving DNS to Cloudflare move my cPanel website?
No. A DNS migration changes authoritative answers. Website files, databases and hosting stay where they are unless a separate hosting migration is performed.
Will my existing email continue to work?
It can, when the required records, direct mail-host resolution and server routing are preserved. Verify independent inbound and outbound delivery instead of relying only on a DNS scan.
Should I keep editing public records in cPanel afterward?
Cloudflare supplies the public authoritative zone after delegation. cPanel’s local zone can still affect its own mail-routing decisions, so coordinate provider-required local settings without treating them as public DNS changes.
How long does the nameserver change take?
It depends on delegation updates and cached record lifetimes. Use authoritative and resolver evidence plus service tests; do not treat one elapsed-time estimate as proof of completion.

