When I first tried setting up DNS in Amazon Web Services Route 53, I thought it would be straightforward—just create a hosted zone, add a record, and my website would magically work. I created a hosted zone with a random name, added an A record pointing to my EC2 public IP, and felt pretty confident.But then I reliazed it doesnt work as simple as I thought it will work like .
No matter what I tried, the domain wouldn’t open in the browser. That’s when I realized I had completely missed something basic—I didn’t even own a domain name. I had been treating Route 53 like it could create a website address for me, when in reality, it only manages DNS for domains that already exist.
That moment was frustrating, but also a turning point. I finally understood how DNS actually works: you need a registered domain first, and then you connect it to Route 53 using nameservers. Without that, there’s nothing for DNS to resolve.
In the end, I learned two important things. First, Route 53 is not a domain provider—it’s a DNS service. And second, if you don’t have a domain, you can still test your app using the EC2 public IP or DNS, which works perfectly for development.
It was a small mistake, but it made the whole concept much clearer. Sometimes, not having something—in this case, a domain—teaches you more than having everything set up correctly from the start.
Creating a hosted Zone in Route 53
Retriving the public IP of EC2 inatance to create a record
Creating Records
Top comments (0)