Skip to content
dnsmigrator

Websupport GoDaddy DNS

Migrate DNS from Websupport to GoDaddy.

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

TTLs below 600s are raised

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

A typical Websupport zone at GoDaddy

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

Websupport GoDaddy

  • TranslatedA@

    192.0.2.70

    TTL 300s is outside the allowed range. Set to 600s.

  • TranslatedAAAA@

    2001:db8::70

    TTL 300s is outside the allowed range. Set to 600s.

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

    Connect Websupport with read-only access (API key + secret (HMAC-SHA1 signed requests)).

  2. 2

    Connect GoDaddy

    Connect GoDaddy (Production API key + 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 GoDaddy

    We snapshot the GoDaddy zone, write in batches, and leave Websupport untouched.

  5. 5

    Verify

    We query GoDaddy'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 Websupport

  • Only A, AAAA, CNAME, MX, TXT and SRV records can be managed; CAA values come back without flags and tag, so CAA records are not read, and NS and ANAME are left alone.
  • Websupport cannot list DNS zones through the API; enter the domain name, and add new domains in the Websupport admin first.
  • Null MX and SRV records without a target are rejected, and trailing spaces in TXT values are stripped.

Access we need: An API key and secret on the Websupport user that owns the domain. Keys have no read-only mode, so the same key is used for preview and apply.

Good to know about GoDaddy

  • DS records can't be changed through GoDaddy's v1 API, so DNSSEC is handled in their dashboard.
  • GoDaddy's DNS API is limited to qualifying accounts. If yours isn't one, export the zone file and we'll use that.
  • The minimum TTL is 600 seconds.
  • Domain forwarding is a GoDaddy web feature, not a DNS record, and isn't migrated.

Access we need: GoDaddy only grants DNS API access to qualifying accounts. Otherwise, export a zone file.

Questions

Will there be downtime moving from Websupport to GoDaddy?

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

No. We never write to Websupport. 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 GoDaddy 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