Use case
Move off a single DNS provider without downtime
Moving DNS usually means a cut-over: export, import, fix what did not translate, change nameservers and hope. With two providers in sync you can add the new one first, watch it agree, and only then decide what to keep.
The problem
- Zone exports never import cleanly: record types, TTL limits and provider-only features differ.
- A nameserver change is visible for as long as resolvers cache the old delegation, so mistakes linger.
- Rolling back means doing it all again in reverse.
How RedundantDNS handles it
- Connect your current provider and adopt the existing zone: RedundantDNS imports its records as the canonical zone.
- Attach the second provider. RedundantDNS creates (or adopts) the zone there and applies the same records, restricted to what both providers support.
- Verify shows whether both providers answer the same records; probes show whether their nameservers answer at all.
- Update the NS set at your registrar to list both providers. The delegation check tells you when the change is visible.
The result
You end with the new provider live next to the old one. Keep both for redundancy, or detach the old one later. Detaching never deletes the provider zone unless you ask and type the zone name.
Plans that fit: Free or Starter. See pricing or how it works.
Other use cases
Put your zone on two providers
Start with one zone and two providers you already have. Free, no card.