Gcore DNS Azure DNS

Migrate DNS from Gcore to Azure DNS.

8 record types move as they are. 2 things work differently at Azure DNS, 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

Apex CNAMEs need a different shape

Azure DNS doesn't allow a CNAME at the apex and has no alias record for external hostnames. These become static A/AAAA records, which don't follow the target if its IPs change.

HTTPS isn't available

Azure DNS can't store HTTPS records through its API. They're marked Unsupported with the reason, never dropped silently.

A typical Gcore zone at Azure DNS

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

Gcore Azure DNS

ExactA@
192.0.2.70
ExactAAAA@
2001:db8::70
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.
ExactCNAMEwww
example.com.

How each record at Gcore DNS translates to Azure DNS
Status	Type	Name	At Azure DNS	TTL
Exact	A	@	192.0.2.70	5m
Exact	AAAA	@	2001:db8::70	5m
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	CNAME	www	example.com.	1h

How the move works

1
Connect Gcore
Connect Gcore with read-only access (Permanent API token).
2
Connect Azure DNS
Connect Azure DNS (Service principal (client ID + secret)). 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 Azure DNS
We snapshot the Azure DNS zone, write in batches, and leave Gcore untouched.
5
Verify
We query Azure DNS'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 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.

Good to know about Azure DNS

Azure alias records point at Azure resource IDs, which don't exist outside Azure.
Apex CNAMEs are not allowed. Use an alias record to an Azure resource or A/AAAA records.

Access we need: Reader on the DNS zone for the preview, DNS Zone Contributor to apply.

Questions

Will there be downtime moving from Gcore to Azure DNS?

Not if both providers serve the same answers during the switch. The records are copied to Azure DNS 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 Gcore?

No. We never write to Gcore. 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 Azure DNS and publish its new DS record. The cutover plan walks you through each step.

Ready to see your own zone?

Start a free preview