After launching a web server, accessing it via IP address works — but it’s not practical. So the next step was to connect a domain name.
For this, I used Amazon Route 53 from Amazon Web Services.
Why DNS Matters
Humans prefer domain names, not IP addresses. DNS translates a domain into the correct server location.
Without it, users would have to remember numeric IPs — which isn’t realistic.
Step 1: Creating a Hosted Zone
Inside Route 53:
•I created a Public Hosted Zone
•Entered my domain name
AWS automatically generated:
NS (Name Server) records
SOA record
These are essential for DNS
functionality.
Step 2: Mapping Domain to Server
To connect my domain to the EC2 instance:
•Created an A Record
•Pointed it to the server’s public IP
This step tells AWS where to send incoming traffic.
**Step 3: **DNS Propagation
Even after correct setup, the domain didn’t work immediately.
This is expected.
DNS changes take time to propagate globally. In my case, it took some time before everything worked properly.
Challenges I Noticed
Expected instant results after configuration
Needed to double-check record values
Realized DNS delays are normal, not errors
What I Learned
DNS is a critical layer between users and servers
Small configuration mistakes can break routing
Patience is required due to propagation delays
Final Thoughts
Setting up DNS made my project feel more real. Instead of accessing a raw IP, I now understand how domains connect users to applications.
If you're learning cloud, don’t stop at launching a server — connect it properly using DNS.
Top comments (0)