About Expertise Work Managed Apps
Business Website Online Store Sales CRM Team Drive Online Academy Newsletter System Booking System Shared Inbox Knowledge Base Short Links Business Manager Photo Gallery Survey Platform Community Forum Project Boards Estate Agency Car Workshop Restaurant Clinic Photography Studio
AWS
Assess & advise Build & migrate Automate & operate Secure & comply Urgent & go-live
Projects
Hosted Monitoring & Dashboards Self-Hosted Observability Stack Bulk Document Data Extraction Email Deliverability Diagnosis & Repair SEO Migration Recovery AWS Security Review VPS Hardening & ModSecurity Cloud Architecture & Resilience Review SSL & Server Configuration Container Security Review DNS & Email Troubleshooting DevOps Deployment & Rollback Review WordPress Hardening Retainer Data Pipeline Rerun Review Metric Reconciliation
Free Tools
Website Health Check Email Domain Health Check DNS Health Check SSL Certificate Checker Redirect Chain Checker Robots.txt Checker XML Sitemap Validator Docker Compose Checker WordPress Security Check AWS IAM / S3 Policy Checker Domain Registration Lookup Uptime Monitoring Trial Downtime Cost Calculator AWS Cost Estimator Cloud Architecture Self-Assessment DevOps Engagement Builder Self-Managed VPS vs Managed AWS
Blog Certifications Hire Me

Route 53 DNS Migration

A zone moved with every record accounted for, and the TTLs lowered before the change rather than after.

Price and scope

From $199

Typically $199–$399, fixed in writing before anything starts.

1–2 days
Working days, counted from the moment I have access — not from the day you agree.

What moves it up

  • Live mail on the domain, where a missing record stops delivery rather than a website
  • More than about thirty records, or subdomains delegated somewhere else
  • A cutover that has to happen inside a specific window

Some of this you can check yourself, right now, for free: DNS Health Check →

What is missing from a hand-rebuilt DNS zoneSix records in the source zone beside the same zone recreated by hand. The A, CNAME and MX records were copied. The SPF, DKIM and service verification TXT records were not.the records that serve web pages are the ones people rememberSOURCE ZONERECREATED BY HANDA @A @CNAME wwwCNAME wwwMX 10 mailMX 10 mailTXT v=spf1 ...missingTXT s1._domainkeymissingTXT site-verifymissing
Route 53 DNS Migration

What actually goes wrong

The zone gets rebuilt by hand at the new provider and about ninety per cent of it is correct, because the records people remember are the ones that serve web pages. What goes missing is everything that is not a website: the SPF record, the DKIM selector, and the verification TXT for some service that will keep working for weeks and then quietly stop. And because nobody lowered the TTL first, the mistake is cached for a day — so the fix, when it comes, is also invisible for a day.

How I find it

  • dig +noall +answer @<current-nameserver> <domain> ANY — and every record type separately, because ANY is often refused
  • A record-by-record diff of the exported zone against what was created at the destination
  • dig +trace <domain> from outside the network, confirming delegation rather than a cached answer
  • The TTL on every record lowered and allowed to expire BEFORE the nameserver change, not during it

What you get

  • The hosted zone created with every record from the source, diffed rather than retyped
  • Mail records verified as sending — SPF, DKIM and DMARC checked against a real message
  • TTLs lowered ahead of the switch and restored after it, so a mistake is minutes rather than a day
  • Health checks and alias records where they remove a hop or a hardcoded IP
  • The old zone left in place until the new one is confirmed authoritative everywhere

Questions

Can DNS be moved without any interruption?

Yes, if the old zone is left serving until the new one is confirmed. Both sets of nameservers answer identically for the overlap, so it does not matter which a resolver reaches. What causes outages is deleting the old zone the same afternoon.

Do I have to move my domain registration too?

No, and usually you should not do both at once. Nameservers and registrar are separate things — you can point a domain registered anywhere at Route 53. Doing both in one change means an outage has two possible causes.

Why does Route 53 cost anything when my registrar does DNS free?

It is about fifty cents a month per zone plus queries, and for most domains that is a rounding error. What you get for it is health checks, alias records that track an AWS resource without a hardcoded IP, and an API — none of which a free registrar DNS panel offers.

How long does the change take to reach everyone?

The nameserver delegation itself is governed by the TLD's TTL, typically a day or two, which is why the old zone stays up. Individual records inside the zone move at whatever TTL you set, which is why they get lowered first.

Want this done?

Tell me what you are running and I will come back with a fixed price and a date. If it turns out you do not need this, I will say that instead.

Prefer to talk? Book a free call ↗  ·  Or hire me on Upwork ↗  ·  Typical reply within one business day.

When I answer

Sunday to Thursday, 09:00–18:00 EET. Outside that I will still look, but I will not promise a time.

No 24/7 desk, and I will not pretend otherwise

One person, one time zone. If round-the-clock cover is what you need, you need a team, and I will say so rather than sell you a plan that cannot deliver it.

Your AWS bill stays yours

You pay Amazon directly and you keep control of the account. Nothing here resells your infrastructure or sits between you and your own billing.

A price that starts with "from" is a starting price

Every service page lists exactly what pushes a quote above it, before you ask. You get a fixed number in writing before any work begins.