Websupport ClouDNS
Migrate DNS from Websupport to ClouDNS.
6 record types move as they are. Nothing else needs special handling.
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
A straightforward move.
A typical Websupport zone at ClouDNS
Example records for example.com. Open any flagged row to read why it changed.
Websupport ClouDNS
- 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.
| Status | Type | Name | At ClouDNS | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Exact | AAAA | @ |
| 5m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect Websupport
Connect Websupport with read-only access (API key + secret (HMAC-SHA1 signed requests)).
- 2
Connect ClouDNS
Connect ClouDNS (API user auth ID (or sub-user ID/name) + password). Write access is only used when you apply.
- 3
Review the preview
Check every record marked Review or Unsupported. Each one explains what changes and why.
- 4
Apply to ClouDNS
We snapshot the ClouDNS zone, write in batches, and leave Websupport untouched.
- 5
Verify
We query ClouDNS's own nameservers for every record and compare the answers before you switch.
- 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 ClouDNS
- TTLs must be one of ClouDNS's fixed values (60, 300, 900, 1800, 3600, 21600 … 2592000); other TTLs are rounded up.
- Web redirects (CLOUDNS_WR) are ClouDNS-only and are written as plain 301 redirects without frame options.
- The API is rate limited to about 20 requests per second per IP, so large zones apply record by record and take a while.
Access we need: A read-only API sub-user with the zones delegated is enough for the preview; applying needs a read-and-write sub-user or a main API user.
Questions
Will there be downtime moving from Websupport to ClouDNS?
Not if both providers serve the same answers during the switch. The records are copied to ClouDNS 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 ClouDNS and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview