🗺️Set Up Route 53 DNS — Point Your Domain to AWS Route 53

When hosting your website on AWS — whether it’s WordPress on Lightsail, static hosting on S3, or using CloudFront — the final step is pointing your domain to AWS Route 53.
This ensures your DNS records are fully managed within AWS, enabling faster performance, reliable routing, and seamless integration with services like CloudFront, SES, and API Gateway.
🚀This guide walks you step-by-step through:
- Creating Route 53 Hosted Zones
- Adding A, AAAA & CNAME records
- Updating Name Servers in Namecheap, GoDaddy & others
- Confirming DNS propagation (with online tools)
🟢Let’s get started.
1️⃣ Create a Hosted Zone in Route 53
- Go to AWS Console → Route 53
- Click Hosted Zones
- Click Create Hosted Zone
- Enter your domain name:
example.com - Type: Public Hosted Zone
- Click Create
AWS instantly creates:
- 4 NS (Name Server) records
- 1 SOA record
These NS records are what you must copy to Namecheap/GoDaddy.
2️⃣ Create DNS Records in Route 53
If you do not have a Lightsail/EC2 instance or a Cloudfront distribution as of now, then go ahead and skip this step.
Go to AWS Console → Route 53 → Hosted Zones → Select your domain → Create Record
You will typically add:
✅ A Record
Points example.com → Lightsail / EC2 / CloudFront
Type: A (IPv4)
Value: Public IP or CloudFront domain
TTL: 300 Seconds
Routing: Simple
3️⃣ Update Your Domain Registrar with AWS Name Servers
You need to replace your current domain’s NS records with the 4 NS values from Route 53.
They look like:
ns-1023.awsdns-00.org
ns-2047.awsdns-64.com
ns-1832.awsdns-37.co.uk
ns-891.awsdns-47.net
Below are the steps for major registrars.
4️⃣ Update DNS in Namecheap (Step-by-Step)


- Login to Namecheap Dashboard
- Go to Domain List
- Click Manage next to your domain
- Under Nameservers, select:
Custom DNS - Paste the 4 AWS nameservers
- Save changes
⏳ DNS Propagation takes 5 min → 24 hours
(Usually completes in 10–20 minutes.)
5️⃣ Update DNS in GoDaddy (Step-by-Step)


- Login to GoDaddy
- Go to My Products
- Click DNS next to your domain
- Under Nameservers, click Change
- Select Custom
- Enter all 4 AWS nameservers
- Save & confirm
6️⃣ Update DNS in Other Registrars
The process is identical for:
- Hostinger
- Bluehost
- Google Domains (legacy)
- Porkbun
- BigRock
- Name.com
Look for a section called:
“Nameservers” or “Custom Nameservers”
Replace the existing ones with your Route 53 NS records.
7️⃣ Confirm DNS Propagation
After updating, check if your domain is now pointing to AWS.
🔍 Use online propagation checkers
- https://dnschecker.org
- Choose: NS
- Enter domain name
- You should see all AWS name servers resolving globally
Alternative tools:
- whatsmydns.net
- dig (Linux / Mac)
- nslookup (Windows)
If the NS records have propagated, Route 53 is now the authoritative DNS.
8️⃣ Common Issues & Fixes
❗ Domain still shows Namecheap/GoDaddy NS?
Propagation may still be in progress.
Wait 30–60 minutes and check dnschecker.org.
❗ A/CNAME not resolving?
Ensure:
- A-record points to correct Lightsail/EC2 IP
- CloudFront distribution is deployed
- No repeated/duplicate DNS entries in previous registrar
❗ CloudFront + S3 showing 403?
Make sure:
- S3 bucket name = exact domain name
- OAC or public policy is correctly configured
- A-record is Alias → CloudFront distribution
🟩 Summary
| Step | Action |
|---|---|
| 1 | Create Route 53 Hosted Zone |
| 2 | Add A / AAAA / CNAME records |
| 3 | Copy AWS NS records |
| 4 | Update nameservers in Namecheap / GoDaddy |
| 5 | Check propagation using online tools |
| 6 | Domain now fully managed by Route 53 |
