Skip to main content

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​

  1. Akamai Control Center → Identity & Access → Create API client.

  2. Grant the DNS — Zone Record Management API with READ-WRITE access to the zone(s) you will validate against.

  3. Generate credentials. The portal shows you an .edgerc fragment with four lines:

    [default]
    host = akab-xxxxxxxx.luna.akamaiapis.net
    client_token = akab-xxxxxxxxxxxxxxxx
    client_secret = xxxxxxxxxxxxxxxxxxxxxxxx
    access_token = akab-xxxxxxxxxxxxxxxxxxxx
  4. Save — the secret is shown once.

Add the credential​

  1. Settings → DNS Credentials → New → Akamai EdgeDNS.
  2. Paste all four fields from your .edgerc:
    • Host — the host line.
    • Client token.
    • Client secret.
    • Access token.
  3. Test connectivity → Save.

Config fields​

FieldRequiredPurpose
hostyes in practiceEdgeGrid API host from your .edgerc. There is no default — leaving it blank saves without error, but every API call then fails.
client_tokenyesEdgeGrid client token.
client_secretyesEdgeGrid client secret.
access_tokenyesEdgeGrid 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.

See also​