Migrate DNS from Cloudflare to CDB
Moving DNS from Cloudflare to CDB Managed DNS means exporting the zone file, importing records into CDB, then switching authoritative nameservers at the domain registrar. Nameserver changes can take up to 24 hours to propagate, so plan the cutover for a low-traffic window.
TTL preparation
Lower the TTL on critical DNS records in Cloudflare before the cutover. During the migration window, some resolvers still serve records from Cloudflare while the nameserver change propagates. A shorter TTL limits how long those resolvers cache the records, so any corrections to the zone take effect faster.
- Log in to the Cloudflare dashboard and select the domain.
- Navigate to DNS > Records.
- Edit each critical record and set the TTL to 10 minutes (or the lowest available value).
- Wait for the current TTL to expire before continuing, so old cached records stop being served.
If DNSSEC is enabled on the domain in Cloudflare, disable it before switching nameservers. Changing nameservers while DNSSEC is active causes DNSSEC validation to fail, and the domain stops resolving for many clients. Disable DNSSEC in Cloudflare, remove the DS record at the registrar, wait for the DS record TTL to expire, then proceed with the nameserver switch.
- 1
Export DNS records from Cloudflare
Download a BIND zone file from Cloudflare so the same records can be imported into CDB.
- In the Cloudflare dashboard, select the domain and navigate to DNS > Records.
- Click Export to download the DNS records as a BIND zone file (
.txtformat).
Before importing the zone file, review records that were proxied through Cloudflare and confirm their values point to the intended origin server or Orange's CDN endpoint.
- 2
Create a DNS zone in CDB
Create a zone in the CDB Technical Web Portal so imported records have a destination. The zone creation guide covers the same flow with screenshots.
- Navigate to DNS in the Customer Portal and click Add zone.
- Enter the domain name and click Confirm.
- CDB scans and displays any existing DNS records it can detect. Review them, then click Confirm.
Check the Skip scanning box to import all records manually from the Cloudflare zone file in the next step.
- 3
Import DNS records
Import the Cloudflare zone file into the new CDB zone, then review every record before changing nameservers.
- In the All zones tab, open the newly created zone.
- Click Import records.
- In the pop-up, either paste the contents of the Cloudflare zone file directly, or rename the exported
.txtfile to.zoneand click Upload zone file to upload it. - Click Import.
Review the imported records and confirm they look correct. Pay particular attention to records that were previously proxied through Cloudflare and verify that they point to the intended origin server or Orange's CDN endpoint.
Cloudflare supports CNAME flattening, which lets a CNAME record exist at the domain root (
example.com). Standard DNS does not permit CNAME at the apex. Root records that used CNAME flattening in Cloudflare may appear differently in the zone file or after import — check them carefully and confirm they resolve to the expected address.Only DNS records are migrated. Cloudflare CDN, proxy rules, WAF, page rules, redirects, Workers, and SSL/TLS settings are not transferred automatically. Configure those services separately in CDB or another provider after the DNS cutover.
- 4
Update nameservers at the registrar
Point the domain to CDB nameservers by updating the nameserver settings at the domain registrar (the company where the domain was purchased or is managed).
Update the nameserver settings at the domain registrar, not inside Cloudflare. Adding or editing NS records inside the Cloudflare dashboard does not change which DNS provider is authoritative for the domain, because the registrar controls that setting.
Set the nameservers to the following CDB values:
Nameserver Value NS 1 ns1.gcorelabs.netNS 2 ns2.gcdn.servicesLook for a Nameservers or DNS section in the registrar control panel. The exact steps vary by registrar.
- 5
Verify propagation
DNS changes can take up to 24 hours to propagate globally. Check progress in both of these places:
- Use a DNS propagation checker to verify that the domain's NS records resolve to CDB nameservers worldwide.
- In the Customer Portal, a notification appears on the DNS zone until propagation is complete. This is expected and clears automatically.
Once the NS records resolve to CDB, verify that critical migrated records return the expected values:
dig A yourdomain.com dig AAAA yourdomain.com dig MX yourdomain.com dig TXT yourdomain.com dig CNAME www.yourdomain.comCompare the answers against the values in the original Cloudflare zone to confirm the migration is complete.
Keep the Cloudflare DNS zone intact for at least 48 hours after migration. Switching the nameservers back at the registrar provides a rollback path if the CDB configuration needs to be corrected — the rollback is subject to the same DNS propagation delay.