Skip to content
dnsmigrator

Azure DNS Gcore DNS

Migrate DNS from Azure DNS to Gcore.

8 record types move as they are. 2 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

TTLs below 60s are raised

Gcore's minimum TTL is 60 seconds. Shorter TTLs are raised to 60s and shown as translated.

A typical Azure DNS zone at Gcore

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

Azure DNS Gcore

  • UnsupportedA@

    Not migrated

    @ is an alias to an Azure resource. It needs static IP addresses at Gcore.

  • 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.

  • ExactAapp

    192.0.2.30

  • ExactCNAMEwww

    example.com.

How the move works

  1. 1

    Connect Azure DNS

    Connect Azure DNS with read-only access (Service principal (client ID + secret)).

  2. 2

    Connect Gcore

    Connect Gcore (Permanent API token). Write access is only used when you apply.

  3. 3

    Review the preview

    Check every record marked Review or Unsupported. Each one explains what changes and why.

  4. 4

    Apply to Gcore

    We snapshot the Gcore zone, write in batches, and leave Azure DNS untouched.

  5. 5

    Verify

    We query Gcore's own nameservers for every record and compare the answers before you switch.

  6. 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 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.

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 Azure DNS 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 Azure DNS?

No. We never write to Azure DNS. 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.

Related migrations

Ready to see your own zone?

Start a free preview