AWS Route 53 DNS... How does it compare?
DNS is the critical first link in a Website’s ability to load quickly for its users. Cloud solutions don’t mean much if your DNS system isn’t giving you great performance and the level of granulized control you need. High performance and granular control have always been focal points for our business here, and the existing demand for such quality services points to the importance of utilizing a full-service cloud enabling vendor.
A year-or-so ago, Amazon announced the existence of the new Route 53 DNS service. At Total Uptime, we always look at the functionality of services such as these, and how they will generate value for you… the Web-enabled enterprises and SMBs of the world.
What you need to know about AWS’s Route 53…
The Amazon offering is interesting, and what it offers brings up some very important considerations about what Web-enabled businesses are trying to achieve with DNS solutions today.
The first of these considerations is the need for granular control and full management. The Amazon Route 53 solution is simply the bare-bones API, which is what we would expect from AWS, and there is no mention of a user interface included or available – so you, or your developers, need to be ready to roll your own DNS graphical user interface. In addition, integration with other Amazon cloud services is not native at the user-account level, so you will need to call any other Amazon Web Services you use and get your info there, then call Route 53 change requests to point records to say, your “bucket”.
The list of supported records numbers 10…
Ten record types will cover the basics, but who wants to tout their DNS power as “um, we can cover the basics”? (I will take the opportunity to note here that our solution covers 26 DNS record types for total IPv4/IPv6 control.)
Another huge consideration is automatic zone file uploading and record creation. Amazon is saying that you need to get your zone files, and you are then responsible for converting them to the Amazon Route 53 xml data to send the request. Amazon does have a pearl script that you can download that you can use to convert the zone files to their xml. But don’t you want your DNS provider’s system to handle all that for you? Me too – that’s why our DNS system processes zone files automatically. Using Amazon’s DNS would become a bit of a pain if you had 2000 zones to migrate. You or your developer would have to parse each one to xml, then send a separate request, and then get a “pending” status and an API experience that amounts to a “here’s your change receipt, check back later if you don’t get an answer now”. Why would I do all of that when with our DNS I can zip thousands of zone files up and just upload the zip file and let the DNS system do the parsing? Also it will tell me what, if anything is wrong with the DNS records I upload – even remind me to change the authoritative name servers if I forget. So, suffice it to say the Amazon DNS offering is asking you to do the development yourself to get these things done.
It is a good thing that Amazon is jumping into the DNS space and lending credibility to the importance of the service. I mean we all know there are still plenty of folks out there that just aren’t aware of the power of the really good DNS solutions that are available now-days, so having Amazon step into the game will probably get some people who weren’t previously thinking about what they really need from DNS service to succeed going forward. The question for businesses must now become… go with a minimalist approach such as that offered by Route 53, or take advantage of a more complete and automated DNS API and UI with the features and functionality that enterprises today need.
To each their own, but we prefer to focus on delivering the latter.