Understanding AWS Route 53 and DNS for Beginners
In the previous articles we learned about:
VPC
Subnets
Internet Gateway
Route Table
Security Groups
Network ACLs(NACLs)
These components help us build and secure AWS infrastructure.
But there is still one question:
How to users find our application?
For example, when users open "www.amazon.com"
How does the browser know where the website is running?
This is where DNS and AWS Route 53 come into picture.
In this article, we will learn:
What DNS is
Why DNS is needed
What AWS Route 53 is
How AWS Route 53 works
Real-world examples
AWS examples
Let's get started.
Why do we need DNS?
Imagine you want to call your friend.
Would you remember the phone number for every person in your contacts?
Probably not right.
Instead you save names like:
Mom
Dad
Jenny
Kevin
Your phone automatically maps the name to the phone number.
DNS works exactly the same way.
Instead of remembering the IP addresses like:
54.210.100.25
we simply remember:
DNS converts:
Domain Name → IP address
This makes websites easier for humans to use.
What is DNS?
DNS stands for Domain Name System.
DNS is like the phone book of internet.
its job is to convert:
into something computers understand:
54.xx.xx.xx
Without DNS, we would have to remember IP addresses for every websites
How DNS works?
Suppose a user opens:
The process will be like this:
User
↓
DNS Look up
↓
IP Address Found
↓
Application server
DNS finds the IP address associated with the domain name and sends the user to the correct server.
What is AWS Route 53?
AWS Route 53 is Amazon's managed DNS service.
It helps to:
Convert domain name into IP address.
Route users to AWS resources
Improve application availability
Register domain names.
Simply we can that:
Route 53 is AWS's DNS service
Why is it called Route 53
DNS communication uses PORT 53.
This is why AWS named the service "Route 53"
How Route 53 works?
Suppose you have a website:
Your application is running behind a load balancer.
When users enter the domain name, Route 53 finds the correct destination.
Flow:
User
↓
www.shoppingworld.com
↓
Route 53
↓
Load Balancer
↓
Application server
Route 53 doesn't host your application.
Its job is only to direct the users to the correct resource.
AWS Example
Suppose your architecture looks like this:
Public Subnet:
- Load Balancer
Private Subnet:
- Application server
Users do not know the IP address of your Load Balancer.
Instead they simply visit "www.shoppingworld.com"
Route 53 translates the domain name and forwards user to the load balancer.
The Load Balancer then sends the request to the Application server.
Benefits of Route 53
Route 53 provides:
High Availability
Scalability
Managed DNS service
Domain Registration
Health Checks
Because AWS manages Route 53, we do not need to maintain DNS servers ourselves.
Conclusion
DNS is one of the fundamental building blocks of the internet.
Without DNS, users would have to remember the IP addresses for every website.
AWS Route 53 simplifies this process by providing a highly available and scalable DNS service.
Additional Resources
If you want to explore AWS Route 53 in more detail, you can refer to the official AWS documentations:
This article covers Route 53 fundamentals for beginners. The official AWS documentation provides deeper explanation and advance features.
What's Next?
The next article is going to be interesting one.
We will build a complete AWS VPC project that can be added to your resume.
This project is inspired by concepts learned from Abhishek Veeramalla's AWS learning series that I am currently following. I will be implementing the project step by step while explaining the concepts in my own words.
🚀 See you in the next article.