Moving DNS away from Cloudflare and removing a zone

Export the current DNS records and review Cloudflare-dependent Workers, redirects, certificates, security and caching. Confirm the registrar allows the intended nameserver change; domains registered through Cloudflare Registrar have additional requirements.

1. Create the complete DNS zone at the destination provider, including mail, verification and service records. Verify the origin has a publicly trusted certificate if visitors will connect directly.
2. Plan DNSSEC carefully. Remove or replace registrar DS information in the correct order for the new provider so stale validation data does not break resolution.
3. Change registrar nameservers to the destination’s exact set and verify authoritative answers, websites and two-way email as caches expire.
4. Only after the replacement is working, open the Cloudflare zone’s Overview and use Advanced Actions > Remove from Cloudflare where shown. Review subscription effects before confirming.
5. Retain the exported configuration and migration records. Remove obsolete rules or resources only after their replacements are confirmed.

The domain should resolve through the new authoritative provider and all required services should work independently of the removed zone.

For short diagnostics, pausing Cloudflare may be more suitable than deleting the zone, but it still changes the traffic path. Do not disable domain auto-renewal merely to stop using Cloudflare DNS. If the domain is registered there, follow the registrar’s supported transfer or configuration process.

• Connecting a hosted domain to Cloudflare without breaking email
• Checking whether Cloudflare is active for a hostname
• Changing or removing MX records during an email migration
• Exporting a Cloudflare DNS zone before migration

• Cloudflare documentation