Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« Amazon SimpleDB BatchDelete | Main | AWS Achieves PCI DSS 2.0 Validated Service Provider Status »


TrackBack URL for this entry:

Listed below are links to weblogs that reference Amazon Route 53 - The AWS Domain Name Service:


Feed You can follow this conversation by subscribing to the comment feed for this post.

Fred Janon

> For example, you could create a new sub-domain for each new customer of a Software as a Service (SaaS) application


Basit Mustafa

How do you set MX records? Documentation is pretty mute on this...setting Type element to MX, Value to ### mxhost. , but the validation engine doesn't like that I haven't included a Name element...what goes here? It's an MX record, it doesn't resolve to a name...but it won't take junk/empty element...

M. David Peterson

Dear Jeff: The LOVE in my heart right now... [thump,thump... thump, thump...] I can not describe it words which you of all people knows is saying a lot.

YES!!!!! This is exactly what we've been waiting for. Gracias, my friend and to the rest of my friends@AWS!


Why would you create a subdomain for each of your SaaS customers, and not just use a wildcard?


That's definitely a nice service, but in my opinion slightly overpriced. Most traditional domain wholesalers have DNS with API access included in the registration fee of the domain. While 12 $ per year for a domain might seem not much, it's 100% on top of the domain price of around 12 $ per year.

Besides the pricing issue, I'd love to switch all of our domains to your new AWS DNS. Any plans for lower pricing for many domains? Or maybe even something like a "reserved instance" pricing or flat free pricing for say 100/500/1000/5000/10000 domains?

Maciej Wiercinski

Seems to be great, especially compared to DynDNS' Custom product, more value for less money and more scalable as well. Nothing on geographical anycast though.

Jeff Barr

E.T., a wildcard domain wouldn't work if the subdomains were to be routed to more than one EC2 instance.

Jeff Barr

Hi Basit, here's an AWS Forum thread with the necessary info: .

Chris Cera

I know a ton of time and debate goes into naming a product or service, but I think "53" is too visually similar to "S3" and will cause confusion. I would consider dropping this name long-term and just calling it "Amazon DNS" or similar. My $0.02.


I agree about the naming. Why was it called Route 53? Whats the significance of that?


I agree with Ted. I would love to use this service, but it’s going to be too expensive for us. We have many low-traffic domains, and the $1/month/domain unfortunately is going to add up to too much.


Id love this new service however intergration into the AWS Console with an easy UI, would be awesome, compeitors provide a nice web UI, it seems this service requires more XML hardcoding, for someone who prefers web UIs, an additon of a Web UI in the mangement console would be awesome!.


Is it $1month/hosted zone (could be many domains) or $1 month/domain?

John Alessi

The significance of the Route 53 name is that DNS normally uses port 53 for network communications.

Thomas Bodetti

This is really interesting, I understand most of how this works, but I sort of do not understand how to setup the service, looks like a command line tool or something like that, sort of confusing, but interesting.


Hi Thomas,

Thanks jeff! it is really well described for amazon route 53. I am one of the developer of DNS30 - web based user interface for Amazon route 53.

The comments to this entry are closed.

Featured Events

The AWS Report

Brought to You By

Jeff Barr (@jeffbarr):

Jinesh Varia (@jinman):

Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30