Gigahost
Gigahost API key setup: create a `flux_live_…` personal API key with DNS mode `r` for preview or `rw` for apply.
On this page
Gigahost API key permissions
- Credential type
- Personal API key
- Preview access
- dns mode r (read-only), limited to the required zone IDs where possible.
- Apply access
- dns mode rw (read-write), limited to the required zone IDs where possible.
- API endpoint
- DNSMigrator uses the provider's fixed API endpoint.
Additional access
DNSControl id
{
"TYPE": "GIGAHOST"
}Create credentials
Create a flux_live_… personal API key with DNS mode r for preview or rw for apply.
Access you'll grant
dns mode r (read-only), limited to the required zone IDs where possible.
dns mode rw (read-write), limited to the required zone IDs where possible.
Before you start
- A Gigahost Flux account with access to the DNS zones.
- An admin session; Gigahost's API-key management endpoints are admin-only.
Setup steps
0 of 6 done
Open API keys
Sign in to the Flux Control Panel, open the account area, and select API keys. Use an administrator session to manage personal keys.
Create a personal key
Create a key with a recognizable label and, for a migration-only credential, an expiry in the future. Gigahost documents the API fields as
labeland optionalexpires_at.Choose the DNS mode
Set the
dnspermission category to moderfor preview only orrwto apply. Do not add server, webhosting, rack, support, billing, or account permissions.Preview moderApply moderwLimit the zone resources
For existing zones, choose specific DNS zone IDs (
all: false) and select only the zones being moved. Choose all DNS zones (all: true) only if DNSMigrator needs to create a destination zone.Specific zonesall: falseAll zonesall: trueCreate and copy the secret
Create the key and copy the full secret immediately. Gigahost shows it only at creation or rotation; later pages show only key_prefix. Production keys begin with
flux_live_.Production prefixflux_live_Paste the API key
Paste the complete secret into API key. Do not paste the shortened key_prefix shown in the key list.
Troubleshooting
The key format is rejected
Paste the complete secret shown at creation or rotation. The shortened key_prefix is not a credential; production secrets begin with flux_live_.
The zone list is empty or a zone returns 403
Edit the key's dns resource restriction so the required zone ID is selected, or recreate it with the correct IDs.
Preview works but apply returns 403
The key is in dns mode r. Change its complete permissions object to use dns mode rw while keeping other categories absent.
DNSMigrator cannot create the destination zone
A specific-ID key cannot include a zone that does not exist yet. Temporarily use dns mode rw with all DNS zones, create the zone, then restrict the key to the new zone ID.
Official documentation
Guide checked against the official documentation on .
Credential fields
| Field | Requirement | Where to find it |
|---|---|---|
| API keyapiKey | Required | The full one-time personal API-key secret beginning flux_live_, not the key_prefix returned by later list or detail views. |
Capabilities
- Create zones
- Yes
- List zones
- Yes
- DNSSEC
- Managed through the API
- Minimum TTL
- 60 seconds
- Apex CNAME
- No
- Read only
- No
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- PTR
- ALIAS
- DNAME
- TLSA
Caveats
- 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.
Troubleshooting
- The key format is rejected
- Paste the complete secret shown at creation or rotation. The shortened key_prefix is not a credential; production secrets begin with flux_live_.
- The zone list is empty or a zone returns 403
- Edit the key's dns resource restriction so the required zone ID is selected, or recreate it with the correct IDs.
- Preview works but apply returns 403
- The key is in dns mode r. Change its complete permissions object to use dns mode rw while keeping other categories absent.
- DNSMigrator cannot create the destination zone
- A specific-ID key cannot include a zone that does not exist yet. Temporarily use dns mode rw with all DNS zones, create the zone, then restrict the key to the new zone ID.