Gigahost Azure DNS

Migrate DNS from Gigahost to Azure DNS.

9 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
PTR

Alias records are converted

Gigahost alias records become CNAMEs below the apex. At the apex they need static addresses, and the preview shows which ones.

DNAME, TLSA aren't available

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

A typical Gigahost zone at Azure DNS

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

Gigahost 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 Gigahost 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 Gigahost
Connect Gigahost with read-only access (Personal API key (Bearer flux_live_…)).
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 Gigahost 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 Gigahost

DNSSEC can only be switched on through the API for .no domains registered with Gigahost.
Null MX records and TXT values with leading or trailing spaces are rejected or trimmed by the API.
Redirects are separate objects and aren't migrated as DNS records.

Access we need: An API key with DNS read permission for the preview and DNS write to apply, optionally limited to specific zone IDs.

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 Gigahost 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 Gigahost?

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