Skip to content
dnsmigrator

Akamai Edge DNS INWX

Migrate DNS from Akamai to INWX.

15 record types move as they are. 2 things work differently at INWX, 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
  • CAA
  • PTR
  • HTTPS
  • SVCB
  • TLSA
  • SSHFP
  • NAPTR
  • ALIAS

TTLs below 300s are raised

INWX's minimum TTL is 300 seconds. Shorter TTLs are raised to 300s and shown as translated.

A typical Akamai zone at INWX

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

Akamai INWX

  • ExactA@

    192.0.2.70

  • ExactAAAA@

    2001:db8::70

  • ExactMX@

    10 mx1.mail.example.net. +1

  • ExactTXT@

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

  • ExactCAA@

    0 issue "letsencrypt.org"

  • 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 INWX

    Connect INWX (Username + password session login, with optional TOTP 2FA secret). 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 INWX

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

  5. 5

    Verify

    We query INWX'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 INWX

  • TTLs must be between 300 seconds and 10 days.
  • Each record value is a separate API call, and INWX limits login attempts, so large zones apply slowly.
  • Accounts with 2FA need the TOTP shared secret, which stores both factors together.

Access we need: A sub-account with nameserver view rights for the preview; nameserver edit (and DNSSEC) rights to apply.

Questions

Will there be downtime moving from Akamai to INWX?

Not if both providers serve the same answers during the switch. The records are copied to INWX 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 INWX 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