How to setup Amazon Route 53 DNS

by Ruchira on June 8, 2013

amazon-route-53Amazon offers many cloud services with their Amazon Web Services brand and Amazon Route 53 is the premium DNS services on AWS. Lots of interesting things can be done with Route 53 other than just hosting your records. Route 53 offers services such as DNS based load balancing, DNS fail over, Health checks etc. Route 53 uses anycast technology to serve records to the users with minimum latency by routing the requests to the nearest server to the user. They have many DNS pop’s (point of presence) on various parts of USA,Europe and Asia so your visitors expect a little bit of a boost in loading speed of your sites. I have been using Linode’s own DNS service for the past 3 years for all of my web sites but since Route 53 is so cheap and promising thanks to anycast, I have decided to use Route 53 DNS for this blog. Here’s how I set it up 

Setting up Amazon S3 is really simple just signup and log in to AWS console’s Route 53 section.




Click the “Create Hosted Zone” button and you need to enter your domain name when asked and if you like add information about it on the “comment” box. After clicking the create button, it will display a set of DNS server addresses to add on your domain registrar. So go ahead and add those records as name servers.

Now click “Go to Record Sets” and that’s where you need to setup your A,AAAA,MX,CNAME records and all that. Click “Create a Record Set” button and basically next steps are self explanatory. You can specify TTL values and routing policies. Keep routing policy as “Simple” if you are using Route 53 as basic DNS server.

And its all done! Now your website will be slightly faster for the end visitors thanks to anycast technology.

I'm Ruchira Sahan and all posts on this blog are completely my thoughts and writings. I love DIY and Technology. So feel free to contact me for anything about this blog and don't forget to add a comment if this blog helped you! Thanks
View all posts by Ruchira

{ 2 comments… read them below or add one }

1 Aryo June 9, 2013 at 8:04 AM


Is it same like cloudflare or Rackspace Cloud DNS? Because for the most Cloud DNS has similar issue with some time the files couldn’t be access time so should me count for the TTL precisely at certain time the cache should be purge in the edge network.


2 Ruchira June 9, 2013 at 8:32 AM

Route 53 has many functions like I stated on the post. It acts like a plain old DNS server if you set the routing policy to simple.


Leave a Comment

Previous post:

Next post: