Skip to content
dnsmigrator

Akamai Edge DNS GidiNET

Migrate DNS from Akamai to GidiNET.

7 record types move as they are. 2 things work differently at GidiNET, 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

Alias records are converted

Akamai alias records become CNAMEs below the apex. At the apex they need static addresses, and the preview shows which ones.

A typical Akamai zone at GidiNET

Example records for example.com. Open any flagged row to read why it changed.

Akamai GidiNET

  • ExactA@

    192.0.2.70

  • ExactAAAA@

    2001:db8::70

  • ExactMX@

    10 mx1.mail.example.net. +1

  • ExactTXT@

    "v=spf1 include:_spf.example.net -all"

  • UnsupportedCAA@

    Not migrated

    GidiNET doesn't support CAA records through its API.

  • ExactTXT_dmarc

    "v=DMARC1; p=reject; rua=mailto:dmarc@example.com"

  • ExactSRV_sip._tls

    100 1 443 sip.example.net.

  • ExactCNAMEwww

    example.com.

How the move works

  1. 1

    Connect Akamai

    Connect Akamai with read-only access (EdgeGrid API client (host, client token, client secret, access token)).

  2. 2

    Connect GidiNET

    Connect GidiNET (Username + dedicated API password (SOAP)). Write access is only used when you apply.

  3. 3

    Review the preview

    Check every record marked Review or Unsupported. Each one explains what changes and why.

  4. 4

    Apply to GidiNET

    We snapshot the GidiNET zone, write in batches, and leave Akamai untouched.

  5. 5

    Verify

    We query GidiNET's own nameservers for every record and compare the answers before you switch.

  6. 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 GidiNET

  • TTLs are limited to fixed steps (60 s to 2 days); other values are rounded up to the next allowed step.
  • CAA records are only available on the premium DNS service and aren't managed by DNSMigrator.
  • Apex NS records and read-only system records can't be changed through the API.

Access we need: The API password has full account access; generate a dedicated one and revoke it after the move.

Questions

Will there be downtime moving from Akamai to GidiNET?

Not if both providers serve the same answers during the switch. The records are copied to GidiNET 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 GidiNET and publish its new DS record. The cutover plan walks you through each step.

Related migrations

Ready to see your own zone?

Start a free preview