Cloudflare DNS Gcore DNS

Migrate DNS from Cloudflare to Gcore.

9 record types move as they are. 4 things work differently at Gcore, and the preview shows exactly which of your records they affect.

Free preview. Read-only. Nothing changes until you apply.

What works differently

Generated from the same provider capability data the migration engine uses.

Moves as-is

A
AAAA
CNAME
MX
TXT
NS
SRV
CAA
HTTPS

Proxied records lose the CDN

Gcore has no equivalent of Cloudflare's proxy. Proxied records move as plain records pointing at your origin, which exposes the origin IP. Put a CDN in front before cutting over if that matters.

CF_REDIRECT, CF_TEMP_REDIRECT, CF_SINGLE_REDIRECT, CF_WORKER_ROUTE, PTR, DS, SVCB, TLSA, SSHFP, NAPTR, LOC, CERT, URI aren't available

Gcore can't store CF_REDIRECT, CF_TEMP_REDIRECT, CF_SINGLE_REDIRECT, CF_WORKER_ROUTE, PTR, DS, SVCB, TLSA, SSHFP, NAPTR, LOC, CERT, URI records through its API. They're marked Unsupported with the reason, never dropped silently.

"Auto" TTLs get a real value

Cloudflare's automatic TTL has no equivalent, so those records get Gcore's default of 3600s.

Domains registered at Cloudflare must transfer out

Cloudflare Registrar only allows Cloudflare's nameservers. If the domain is registered there, transfer it to another registrar before switching.

A typical Cloudflare zone at Gcore

Example records for example.com. Open any flagged row to read why it changed.

Cloudflare Gcore

ReviewCNAME@
app.example-host.net.
TTL was "auto". Set to 3600s.
ExactMX@
10 mx1.mail.example.net. +1
ExactTXT@
"v=spf1 include:_spf.example.net -all"
ExactCAA@
0 issue "letsencrypt.org"
ExactTXT_dmarc
"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
ExactSRV_sip._tls
100 1 443 sip.example.net.
ExactAmail
203.0.113.25
ReviewAshop
203.0.113.10
TTL was "auto". Set to 3600s.
ExactCNAMEwww
example.com.

How each record at Cloudflare DNS translates to Gcore DNS
Status	Type	Name	At Gcore	TTL
Review	CNAME	@	app.example-host.net.	1h
Exact	MX	@	10 mx1.mail.example.net. 20 mx2.mail.example.net.	1h
Exact	TXT	@	"v=spf1 include:_spf.example.net -all"	1h
Exact	CAA	@	0 issue "letsencrypt.org"	1h
Exact	TXT	_dmarc	"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"	1h
Exact	SRV	_sip._tls	100 1 443 sip.example.net.	1h
Exact	A	mail	203.0.113.25	5m
Review	A	shop	203.0.113.10	1h
Exact	CNAME	www	example.com.	1h

How the move works

1
Connect Cloudflare
Connect Cloudflare with read-only access (Scoped API token).
2
Connect Gcore
Connect Gcore (Permanent API token). Write access is only used when you apply.
3
Review the preview
Check every record marked Review or Unsupported. Each one explains what changes and why.
4
Apply to Gcore
We snapshot the Gcore zone, write in batches, and leave Cloudflare untouched.
5
Verify
We query Gcore's own nameservers for every record and compare the answers before you switch.
6
Switch nameservers
Lower TTLs a day or two ahead, remove any DS record if DNSSEC is on, then point the domain at the new nameservers at your registrar.

Good to know about Cloudflare

Proxied (orange-cloud) records hide the origin IP. Moving them to another provider sends traffic straight to the origin.
Apex CNAMEs are flattened by Cloudflare. Other providers need an ALIAS record or static A/AAAA records instead.
Cloudflare Registrar only allows Cloudflare nameservers, so domains registered there must be transferred out first.

Access we need: Zone → DNS → Read for the preview, Zone → DNS → Edit to apply.

Good to know about Gcore

Record sets that use GeoDNS or balancing filters, failover health checks, answer metadata or disabled answers are flagged and never changed by us.
SRV records can't have an empty target, and PTR records only work in reverse-DNS zones.
ALIAS records are written as CNAMEs, which Gcore flattens at the zone apex.

Access we need: A permanent API token whose role can manage DNS. Gcore tokens can't be limited to read-only DNS.

Questions

Will there be downtime moving from Cloudflare to Gcore?

Not if both providers serve the same answers during the switch. The records are copied to Gcore and verified before you change nameservers, so resolvers get the same answer from either side while caches expire.

Do I have to delete anything at Cloudflare?

No. We never write to Cloudflare. Keep the old zone for a week after cutover so you can switch back instantly if anything looks wrong.

What about DNSSEC?

If DNSSEC is on, remove the DS record at your registrar and wait for it to expire before switching nameservers. Then enable DNSSEC at Gcore and publish its new DS record. The cutover plan walks you through each step.

What happens to Cloudflare proxied records?

They move as ordinary records pointing at your origin server, because Gcore can't proxy traffic. The preview lists every proxied record and the IP it would expose.

Ready to see your own zone?

Start a free preview