Skip to content
dnsmigrator

Name.com Akamai Cloud (Linode) DNS

Migrate DNS from Name.com to Linode.

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

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

A typical Name.com zone at Linode

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

Name.com Linode

  • 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 Name.com

    Connect Name.com with read-only access (Username + API token (Core API, HTTP Basic)).

  2. 2

    Connect Linode

    Connect Linode (Personal access token). 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 Linode

    We snapshot the Linode zone, write in batches, and leave Name.com untouched.

  5. 5

    Verify

    We query Linode'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 Name.com

  • Only A, AAAA, ANAME, CNAME, MX, NS, SRV and TXT records are supported (no CAA or PTR).
  • The minimum TTL is 300 seconds and TXT values are limited to about 512 characters.
  • Only domains registered at Name.com can be managed, and apex NS records follow the domain's nameservers.

Access we need: Name.com API tokens are account-wide with no read-only scope; the same token is used for preview and apply.

Good to know about Linode

  • Linode only accepts fixed TTLs (30s, 2m, 5m, 1h, 2h, 4h, 8h, 16h, 1d, 2d, 4d, 1w, 2w, 4w). Other values are rounded up.
  • CAA records always have flag 0 and only the issue, issuewild and iodef tags.
  • Linode DNS Manager doesn't support DNSSEC, so turn it off at the registrar before switching nameservers.

Access we need: Domains: Read Only for the preview; Domains: Read/Write to apply.

Questions

Will there be downtime moving from Name.com to Linode?

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

No. We never write to Name.com. 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 Linode 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