Akamai Edge DNS Gigahost
Migrate DNS from Akamai to Gigahost.
11 record types move as they are. 1 things work differently at Gigahost, 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
- TLSA
- ALIAS
DS, HTTPS, SVCB, SSHFP, NAPTR, LOC, CERT, RP, AKAMAICDN, AKAMAITLC aren't available
A typical Akamai zone at Gigahost
Example records for example.com. Open any flagged row to read why it changed.
Akamai Gigahost
- 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.
| Status | Type | Name | At Gigahost | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Exact | AAAA | @ |
| 5m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect Akamai
Connect Akamai with read-only access (EdgeGrid API client (host, client token, client secret, access token)).
- 2
Connect Gigahost
Connect Gigahost (Personal API key (Bearer flux_live_…)). 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 Gigahost
We snapshot the Gigahost zone, write in batches, and leave Akamai untouched.
- 5
Verify
We query Gigahost'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 Akamai
- AKAMAICDN and non-DUAL AKAMAITLC records point at Akamai edge hostnames. Other providers have no equivalent, so recreate them as CNAME or ALIAS records by hand.
- Apex ALIAS records are stored as AKAMAITLC records with the DUAL answer type. ALIAS records below the apex become CNAMEs.
- TXT values can't contain double quotes or backslashes.
Access we need: DNS—Zone Record Management API: READ-ONLY for the preview, READ-WRITE to apply.
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.
Questions
Will there be downtime moving from Akamai to Gigahost?
Not if both providers serve the same answers during the switch. The records are copied to Gigahost 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 Akamai?
No. We never write to Akamai. 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 Gigahost and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview