Public DNS migration to Route 53 .

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