Domains · Practical guide
DNSSEC and DS rollover: migrate your domain without breaking resolution
A DNS provider switch can break signed DNS responses if the parent zone still expects the previous DNSSEC key. Coordinate both sides.
First published · OlaCheap technical reference · Check current provider instructions before changing production services
Identify the two administrators before migrating
A DNSSEC-protected domain has signed records published by its authoritative DNS provider, while the parent zone contains delegation information that validates the child zone. A registrar usually exposes the controls to change the DS record at the parent. Changing one side without coordinating the other can make a healthy site appear unreachable to validating DNS resolvers.
Before any migration, identify the actual registrar, authoritative nameserver provider, DNSSEC signing mode, and the administrators allowed to update each. A domain transfer is not the same as moving DNS service. Do not assume your new provider will automatically remove or replace the parent DS material when nameservers change.
Collect the DNS and DNSSEC baseline
Record the existing nameservers, DS record values, signing key identifiers, and validation results from independent resolvers. Save records for MX, SPF, DKIM, verification TXT, API hosts and website endpoints. A DNSSEC task should not silently change mailbox routing or delete service verification records.
Ask the destination DNS operator for its supported migration procedure, including whether signing keys can be transferred, both providers can sign temporarily, or DNSSEC needs a controlled disable-and-enable cycle. These options are not interchangeable across DNS operators and registries. Use the current procedure for the exact domain and provider.
Coordinate the change and confirm real resolution
Use a documented window with rollback contacts available at both service operators. If DS information must change, confirm the exact value and the intended domain before an authorized administrator submits it. Avoid improvising changes based on a single cached resolver response, which might not show the same state as other networks.
After publishing, use validating resolvers to inspect the chain of trust and test several service hostnames, not only the apex domain. Then verify actual HTTPS and mail delivery. A correct DS record does not mean every DNS application record or mail system was migrated correctly.
Recover carefully and preserve the evidence
If a resolver reports a DNSSEC validation failure, distinguish a parent DS mismatch from an unsigned child, stale delegation information or a provider outage. Follow the registrar and DNS provider's published recovery process rather than repeatedly toggling records without observing the response.
Record the old and new values, timestamps, validation observations, approvals and rollback actions. Recheck after normal cache periods have passed. The acceptance criterion is that external clients can validate and reach the services, not merely that an administrative dashboard shows an Enabled badge.
Next practical step
This article is an educational checklist, not a claim of live product availability or a substitute for current documentation from your provider.
Explore OlaCheap domain tools →References and official documentation
These materials help verify procedures. Provider requirements may change, and this guide does not claim first-hand security certification or independent testing of third-party products.