Foundation · 2 min
What you need to know
How should an ecommerce domain be moved to a new platform?
Inventory current DNS records, verify the new origin and certificate, lower relevant TTLs in advance, and schedule a controlled record change. Check multiple resolvers and keep tested reversal records ready.
What is DNS in an ecommerce migration?
DNS is the naming system that directs the store’s domain and related services to their destinations. During migration, its records are changed, so customer requests reach the new storefront.
What is DNS TTL and why does it matter during migration?
DNS TTL is the period resolvers may cache a record. Lowering it before cutover can shorten how long some users continue reaching the old destination after the record changes.
When should DNS changes be made?
Make DNS changes only after the new production environment, certificates, redirects, monitoring and rollback path pass final checks. Schedule the change when required owners can watch and respond.
How do I reduce downtime during domain cutover?
Prepare and warm the new environment, reduce TTLs early, keep the old store available, and make only the planned record changes. Validate routing from several networks immediately after cutover.
What should happen if domain cutover fails?
Use the documented reversal records if the failure meets rollback criteria, and reversal remains safe. Preserve orders created on either side and reconcile them before normal operation resumes.
A quick store check
Check the storefront and related DNS records from multiple resolvers before and after the scheduled change.
Foundation · 2 min
Frequently asked questions
Does lowering TTL update existing caches immediately?
No. Lower it before cutover and allow the previous TTL to expire where possible.
Should email DNS records be changed with the storefront?
Only when the email design requires it. Inventory and protect unrelated records from accidental changes.