Quick warning before we start

You are about to move a domain from some poor registrar into the cozy world of AWS Route 53. This is perfectly doable and usually less scary than it sounds. Follow the steps and you will keep DNS intact, avoid downtime, and not have to explain to your boss why the site vanished for an hour.

Step 1 Prepare the domain at the current registrar

Do these things first while you still can. If you skip them you will be playing email tag with support and crying into your keyboard.

• Disable domain lock. Registrars often protect domains from theft by locking transfers. Turn that off.
• Turn off privacy protection so approval emails reach the real admin contact.
• Request the authorization code from the current registrar. This is also called an EPP code or transfer key by some vendors.
• Make sure the administrative contact email is valid. Transfers are frequently blocked by outdated WHOIS data.

Step 2 Verify WHOIS and contact details

Confirm the WHOIS info matches the person who can click approval links. If the email or phone number is wrong update WHOIS before starting the transfer. That saves time and annoyance.

Step 3 Plan your DNS and name server strategy

You have two safe options depending on how much risk you like.

Option A Keep the current name servers

Keep name servers pointed at the old DNS host during the transfer. After Route 53 completes you can create a hosted zone there and switch name servers when ready. This minimizes downtime when you want to be conservative.

Option B Migrate DNS records into Route 53 first

Export zone files from the existing DNS provider and import or recreate records in a Route 53 hosted zone. Lower TTL values a few days before switching to speed propagation when you flip name servers.

Step 4 Initiate the transfer in the AWS console

In the Route 53 console request a domain transfer and enter the authorization code. Confirm contact verification and accept transfer fees. AWS will contact the losing registrar and start the process. Expect email updates to the administrative contact.

Step 5 Approve the transfer at the current registrar and monitor progress

Some registrars require an explicit approval step. Look out for that email. Keep an eye on status messages and be ready to respond. Transfers usually complete within a few days but sometimes finish faster.

Step 6 After the transfer completes

• Verify Route 53 has the correct records and name servers.
• If you kept the old name servers switch them to the new Route 53 name servers when ready.
• Raise TTLs back to normal after propagation is complete.
• Confirm WHOIS now reflects AWS as the registrar if you care about that detail.

Common gotchas and how to avoid them

• Expired domain or 60 day transfer lock after recent purchase or change. Check the domain age and recent registrar updates before you try.
• Mismatched admin email in WHOIS. Update it early to avoid approval failures.
• Private registration blocking approval emails. Disable privacy for the transfer window.
• High TTLs. Lower them a couple days before switching to reduce propagation pain.

Recap and final advice

Unlock the domain and get the authorization code. Verify WHOIS and admin contacts. Decide whether to migrate DNS first or keep name servers during transfer. Initiate the transfer in Route 53 and approve any registrar emails. After the move verify records and adjust TTL values. Follow these steps and you will survive with little or no downtime and maybe even some satisfaction at doing it yourself.