Skip to content
DNSmigrator

Hurricane Electric DNS OVHcloud DNS

Migrate DNS from Hurricane Electric to OVHcloud.

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

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

Hurricane Electric to OVHcloud 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
  • HTTPS
  • SVCB
  • LOC
  • NAPTR
  • RP
  • SSHFP

Alias records are converted

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

A typical Hurricane Electric zone at OVHcloud

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

Hurricane Electric OVHcloud

  • 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 Hurricane Electric

    Connect Hurricane Electric with read-only access (Account username + password (+ TOTP)).

  2. 2

    Connect OVHcloud

    Connect OVHcloud (Application key + application secret + consumer key (EU, CA or US API)). 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 OVHcloud

    We snapshot the OVHcloud zone, write in batches, and leave Hurricane Electric untouched.

  5. 5

    Verify

    We query OVHcloud'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 Hurricane Electric

  • Dynamic DNS records keep their own update keys, which can't be read back and must be set again after a move.

Access we need: Hurricane Electric has no API keys or scoped roles; access means full control of the whole account.

Good to know about OVHcloud

  • OVHcloud reads each record with a separate API call, so large zones take a while to load.
  • Changes are published when the zone is refreshed, which we trigger after applying; it can take a few minutes.
  • TXT values can't contain double quotes or backslashes, and ALIAS records aren't supported.

Access we need: GET /domain/zone and GET /domain/zone/* for the preview; POST, PUT and DELETE on /domain/zone/* to apply.

Questions

Will there be downtime moving from Hurricane Electric to OVHcloud?

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

No. We never write to Hurricane Electric. 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 OVHcloud 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