Export the Cloudflare DNS zone before a migration or broad record change. Keep the export with a separate record of proxy and product settings so you can reconstruct the full service configuration.
IN THIS ARTICLE
What you need before you begin
Confirm the correct account and zone, and choose a secure storage location. DNS exports can disclose infrastructure names and verification records even when they do not contain application passwords.
01 Export a Cloudflare DNS zone before migration
- Open DNS > Records for the intended domain.
- Choose Import and Export, then Export, and save the zone file with the domain and date in its filename.
- Open the file locally and check representative A/AAAA, MX, TXT, CNAME and service records against the dashboard.
- Record Cloudflare-specific settings separately, including proxy status, redirects, cache rules, TLS mode and any Workers routes needed by the site.
- When moving to another provider, review its import format and compare the imported zone before changing nameservers. Retain the previous working configuration through the transition.
Confirm the expected result
The file should contain the intended DNS records and be readable by your planned recovery or migration tools. A downloaded file without a review is not yet a verified recovery plan.
Troubleshoot unexpected results
Cloudflare-specific comments or attributes may not have the same meaning at another DNS provider. Do not import an old zone blindly over newer mail or verification changes. DNSSEC parent records also require a separate migration plan.
Does the export include my website files or WAF rules?
No. It is a DNS zone export. Website data, security rules and other Cloudflare products need their own backup, export or configuration record.
.png)
 (1).jpg)
 (1) (1).png)
 (1).png)
.jpg)
.jpg)
 (1).jpg)
.jpg)
