DNS hostingDNS hostingCapabilities verified
Gigahost
Migrate DNS zones to or from Gigahost: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at Gigahost. Free and read-only.
Access we need
- Credentials
- Personal API key (Bearer flux_live_…)
- Permissions
- An API key with DNS read permission for the preview and DNS write to apply, optionally limited to specific zone IDs.
What Gigahost supports
The same data the translation engine uses when it plans a migration.
- Create zones through the API
- List zones through the API
- Turn on DNSSEC through the API
- Apex CNAME (flattening)
- Apex ALIAS record
- Aliases to cloud resources
- CDN proxy on records
- Routing policies
- Minimum TTL
- 60s
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- PTR
- ALIAS
- DNAME
- TLSA
Good to know
- 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.