Skip to content
DNSmigrator

UltraDNS (DigiCert) ClouDNS

Migrate DNS from UltraDNS to ClouDNS.

15 record types move as they are. 2 things work differently at ClouDNS, and the preview shows exactly which of your records they affect.

Free preview. Read-only. Nothing changes until you apply.

UltraDNS to ClouDNS DNS migration differences

Generated from the same provider capability data the migration engine uses.

Moves as-is

  • A
  • AAAA
  • CNAME
  • MX
  • TXT
  • NS
  • SRV
  • CAA
  • PTR
  • ALIAS
  • DS
  • TLSA
  • SSHFP
  • NAPTR
  • SPF

TTLs below 60s are raised

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

A typical UltraDNS zone at ClouDNS

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

UltraDNS 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.

Set up the connections

Use the provider-specific credential guides before you preview, then keep the migration checklist beside the cutover plan.

How the move works

  1. 1

    Connect UltraDNS

    Connect UltraDNS with read-only access (API user name and password (OAuth password grant)).

  2. 2

    Connect ClouDNS

    Connect ClouDNS (API user auth ID (or sub-user ID/name) + password). 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 ClouDNS

    We snapshot the ClouDNS zone, write in batches, and leave UltraDNS untouched.

  5. 5

    Verify

    We query ClouDNS'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 UltraDNS

  • Traffic-management pools (SiteBacker, Traffic Controller, Directional and Simple Load Balancing) are copied as plain answers and flagged; we never change or delete them on UltraDNS.
  • Resource Distribution pools keep their pool settings when we update their answers.
  • ALIAS is written as UltraDNS Apex Alias, which only works at the zone apex, can't coexist with both A and AAAA at the apex, and can't be used in statically signed zones.
  • SOA, apex NS and system-generated records (such as Valimail DMARC records) are managed by UltraDNS and left untouched.
  • Web Forwards and secondary or alias zones aren't migrated; secondary and alias zones are read-only.
  • UltraDNS locks an account after repeated failed logins, so double-check the password before retrying.

Access we need: Create a dedicated API-only user in a group limited to DNS operations (the built-in TECHNICAL group, or a custom group with DNS read and write). A REPORTING or ungrouped user is enough for a read-only preview. The REST API doesn't support multi-factor login, so MFA must be off for this user.

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 UltraDNS 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 UltraDNS?

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

Related migrations

Ready to see your own zone?

Start a free preview