AWS Route 53 Support
Migrating DNS to Route 53 with no downtime.
DNS migrations fail when a record is missed or when cached name server answers outlive the cutover. We copy every record, verify the new zone answers identically, lower TTLs ahead of time and switch name servers in a controlled window.
When You Need This
The situations where this work pays for itself.
Signs it is time
- You are moving DNS from a registrar or another DNS host to Route 53
- A migration must not interrupt email or the website
- You have many records and are afraid of missing one
- You need to move to a new AWS account's hosted zone
- DNSSEC is enabled on the current domain
What you get
- A record-by-record comparison of old and new zones
- The Route 53 hosted zone defined in infrastructure as code
- A dated cutover and rollback plan
- Post-migration monitoring and TTL clean-up
How we do it
A clear, safe process you can follow along with.
1. Inventory the existing zone
We export or query every record: A, AAAA, CNAME, MX, TXT (SPF, DKIM, DMARC, verification), SRV and CAA. We check dig for subdomains the provider does not list, such as delegated sub-zones.
2. Create the hosted zone and import records
We create the public hosted zone, import records through the API or a zone file, and convert eligible apex and AWS-resource records to alias records where useful.
3. Verify the new zone before cutover
We query the Route 53 name servers directly with dig for every record and compare answers with the old provider, so the new zone is proven correct before any delegation changes.
4. Lower TTLs
At least one old TTL period before the move, we lower the NS record TTL and record TTLs at the old provider so a rollback is quick.
5. Handle DNSSEC
If DNSSEC is active, we remove the DS record at the registrar before changing name servers or plan a key handover, because a stale DS record makes the domain fail validation.
6. Switch name servers and monitor
We update the name servers at the registrar to the four Route 53 values, monitor with queries from several resolvers and keep the old zone intact until caches have expired. Then we restore normal TTLs.
Mistakes we help you avoid
Common ways this goes wrong, and what we do instead.
Missing TXT and MX records
Email and verification records are the most commonly forgotten, and failures show up days later.
Forgetting DNSSEC
A leftover DS record at the parent breaks resolution for validating resolvers.
Deleting the old zone immediately
Resolvers cache delegation. Keep the old zone serving until caches expire.
Changing the registrar and DNS host together
Do one change at a time so any fault has one obvious cause.
Frequently Asked Questions
How do I move DNS to Route 53 without downtime?
Recreate and verify all records in a Route 53 hosted zone, lower TTLs, then change the name servers at the registrar while the old zone keeps serving until caches expire.
Do I need to transfer my domain to Route 53?
No. DNS hosting and domain registration are separate. You can keep your registrar and only change its name servers to those of the Route 53 hosted zone.
How long does a name server change take to propagate?
It depends on the TTL of the NS records at the parent and in resolver caches. That is why we lower TTLs beforehand and monitor rather than assume.
Want Help With Migrating DNS to Route 53 with no downtime?
Schedule an appointment. Tell us about your environment and we will outline the safest, highest-value approach.
Schedule Appointment › No commitment required