Public DNS migration to Route 53 .


Hi experts, I would like to migrate my On-prem Public DNS to Route 53. Could you please suggest any best practice guide so i can perform the activities without any downtime. i have few Productions Website running on the same. i have global websites running and cannot afford downtime. Domain hosting will remains running from Other registrar.

Thanks in Advance.

2 Answers
Accepted Answer

Before you start:

  1. Backup Current DNS Records
  2. TTL Adjustment (Lower the Time-To-Live (TTL) for your DNS records to a short duration (e.g., 300 seconds) a few days before migration. This allows changes to propagate faster during and after the migration.)

Step you may find helpful :

  • Set up Route 53 Hosted Zone. (Create a new hosted zone in Route 53 for each domain you are migrating.)
  • Replicate DNS Records. (Manually replicate all existing DNS records (A, CNAME, MX, etc.) in the Route 53 hosted zone. Double-check for accuracy.)
  • Verify Records. (Use Route 53's "Check DNS" feature to verify that your records match your expectations.)
  • Update Name Servers.(Update the name server records at your domain registrar to point to the Route 53 name servers.)
  • Wait for DNS Propagation : (DNS changes take some time to propagate globally. Monitor the propagation using tools like dig or online DNS checking tools.)
  • Test with a Subdomain (Test the migration by updating the DNS for a less critical subdomain first. This helps you identify any issues before updating the main domain.)
  • Update Main Domain (Once you're confident in the migration, update the DNS records for your main domain.)
  • Monitor for Issues.

Here are some relevant AWS documentation links that can guide you through the process:

Getting Started with Amazon Route 53: 

Getting Started Guide

Creating a Public Hosted Zone:

Creating a Public Hosted Zone

Migrating DNS Service for an Existing Domain to Amazon Route 53:

Migrating DNS Service for an Existing Domain to Amazon Route 53

Updating Name Servers for Your Domain:

Updating Name Servers for a Domain

Checking DNS Records with Route 53 Checker:

Checking DNS Records with Route 53 Checker

Route 53 Health Checks and DNS Failover:

Amazon Route 53 Health Checks and DNS Failover

profile pictureAWS
answered 4 months ago
profile picture
reviewed 19 days ago

Thanks @zouhair, anything else need to configure at end user device or Current-On Prem DNS Server.

answered 4 months ago
  • You're welcome.

    Why would you need to set up end-users' devices for public DNS?

    Just keep in mind, the responses provided earlier are general in nature and based on your first question. If there are additional crucial details specific to your environment, it's advisable to either explicitly mention them or seek guidance from a dedicated resource to ensure a comprehensive approach to the migration process.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions