Move your DNS from Cloudflare, GoDaddy or Route 53
Bring your DNS records over in a few minutes: read them through your provider's API with a read-only key, upload the zone file you export, or scan the public DNS. You review every record before it is saved, then change the name servers at your registrar, and the panel checks the switch for you.
Domains and DNS
Move your DNS from Cloudflare, GoDaddy or Route 53
Bring your DNS records over in a few minutes: read them through your provider's API with a read-only key, upload the zone file you export, or scan the public DNS. You review every record before it is saved, then change the name servers at your registrar, and the panel checks the switch for you.
Related topics
What you can do once your DNS is with us.
Move your domain to CDN DNS (Full DNS Transfer)
Serve the whole domain through the CDN, with automatic certificates.
The recommended way is your provider's API with a read-only key.
On DNS Settings press Add a domain and import its records and type the domain.
Follow the steps for your provider, paste the key and press Get the records, or upload a zone file.
Review the statuses, fix the rows that need attention and save.
Expected result: The domain appears in the list with its records, waiting for the name server change.
2
Switch the name servers
The last step happens at your registrar.
If DNSSEC is on, remove the DS record first.
Replace the current name servers with the ones under New nameservers and remove the old ones.
Press Check now, or leave the screen open: it checks again every minute.
Expected result: The screen says your domain now uses cdn.com.tr name servers, and the domain row shows it as active.
Use cases
Your domain's DNS is at Cloudflare, GoDaddy or Amazon Route 53, and you want to manage it in the same panel as your CDN without losing any mail or subdomain records.
Quick workflow
Open DNS Settings and press Add a domain and import its records. The same import runs when you choose Full DNS Transfer for a new domain.
Type your domain. The panel reads its current name servers, recognises the provider and recommends the import for it, for example Import automatically from Cloudflare.
Create a read-only key at your provider with the steps shown next to the field, paste it and press Get the records. The key is used once for this import and is never stored.
No key? Choose another way: Upload a zone file (BIND or CSV, up to 512 KB) exported from your provider, or Scan public DNS, which takes about a minute.
Review the list. Every row has a status such as Ready, Real server, Attention or Invalid. Fix or leave out rows, then save the records.
Change the name servers at your registrar to the ones on the last screen. The screen recognises many registrars, shows the steps in their panel and checks the switch every minute while it is open.
Checks
Cloudflare: the token needs two read permissions, Zone → DNS → Read and Zone → Zone → Read; the button opens Cloudflare's token page with both filled in. For names behind the Cloudflare proxy (orange cloud) the API gives your real server address, marked Real server. A row marked Cloudflare IP carries a proxy address that stops working when the name servers change: enter your server's address there.
GoDaddy: a personal access token with only the domains.domain:read scope is the read-only option. An API key + secret also works but opens the whole GoDaddy account, so delete it as soon as the import is done. If GoDaddy refuses the key, use the zone file: DNS management → Actions → Export Zone File.
Amazon Route 53: create an IAM user without console access, give it the read-only inline policy the panel shows (optionally limited to one Hosted zone ID) and paste its Access key ID and Secret access key. Delete the access key after the import. Alias records are listed with their targets so you can add them by hand.
DigitalOcean and Hetzner have an automatic import too. For any other provider, upload the zone file it exports, or scan the public DNS.
The public scan asks the domain's own name servers about common names and names seen in public sources, and marks each row Verified or Possible. A record only your provider knows about can be missing, so compare the list with your provider's.
Until you change the name servers, your current provider keeps answering. Nothing changes for your visitors while you import and review.
Frequently asked questions
Will my e-mail keep working?
Yes, as long as your MX, SPF, DKIM and other TXT records are in the list before you change the name servers. Compare the saved records with your current provider's before the switch.
DNSSEC is on for my domain. What do I do?
Turn it off at your registrar first by removing the DS record, wait a day, then change the name servers. The last screen reminds you when it sees a DS record.
My domain is registered at Cloudflare.
Domains registered with Cloudflare Registrar keep Cloudflare's name servers. The last screen recognises this and offers Transfer a domain to us; after the transfer you set our name servers yourself. See Register a domain or transfer it to us.
How long does the switch take?
Registrars usually apply a name server change within minutes; some networks remember the old name servers for up to two days. For .tr domains TRABIS publishes changes at set times, and the last screen shows the next one. Keep the records at your old provider for two more days after the switch.
Is my API key safe?
The key is used once to read your records and is not stored. Choose the read-only option your provider offers, and delete the key at the provider when the import is done.
Can I import more records later?
Yes. Import records on the DNS Settings page runs the same import again for a domain you have already added, and you can add single records by hand at any time.