Akamai EdgeDNS
Akamai's EdgeDNS (formerly Fast DNS) uses the EdgeGrid authentication scheme — four credentials from a single .edgerc file. Configure the credential with EdgeGrid-authenticated API access to the DNS Zone Administration API.
Prerequisites
- An Akamai account with the EdgeDNS product enabled on the target zone.
- Permission to create API clients (Identity and Access Management).
Create the API client
-
Akamai Control Center → Identity & Access → Create API client.
-
Grant the DNS — Zone Record Management API with READ-WRITE access to the zone(s) you will validate against.
-
Generate credentials. The portal shows you an
.edgercfragment with four lines:[default]host = akab-xxxxxxxx.luna.akamaiapis.netclient_token = akab-xxxxxxxxxxxxxxxxclient_secret = xxxxxxxxxxxxxxxxxxxxxxxxaccess_token = akab-xxxxxxxxxxxxxxxxxxxx -
Save — the secret is shown once.
Add the credential
- Settings → DNS Credentials → New → Akamai EdgeDNS.
- Paste all four fields from your
.edgerc:- Host — the
hostline. - Client token.
- Client secret.
- Access token.
- Host — the
- Test connectivity → Save.
Config fields
| Field | Required | Purpose |
|---|---|---|
host | no | EdgeGrid API host. Omitting uses the provider's default; usually override with the value from your .edgerc. |
client_token | yes | EdgeGrid client token. |
client_secret | yes | EdgeGrid client secret. |
access_token | yes | EdgeGrid access token. |
Propagation
Akamai is extremely fast globally — typically under 10 seconds. Default settings work.
Troubleshooting
"Permission denied" / 403
API client was created without the DNS — Zone Record Management grant, or with READ-ONLY access. Regenerate with READ-WRITE.
"Invalid signature"
Client-secret mismatch between what you pasted and what Akamai holds. Re-generate the client credentials; the secret is case-sensitive and cannot be partially copied.