Dan Morrill works in Interactive Media and Cloud delivery systems for Comics Forge as the COO. He has been blogging since 2003 covering different emerging technologies, management and information security. Dan works as a founding member of a number of startups, including Startup Academy International and Dead Tree Comics. His interests are in intellectual property protection, piracy, and information security as it applies to cloud computing. He also has a deep interest in media, mobile computing, and education.. His personal blog is here,  his other pro-blog is here .

One response to “Using Route 53 Amazon’s DNS Service for the Cloud”

  1. Lee Zen

    Thanks for providing an introduction on using Route 53 and why people ought to think about moving their DNS off premise and into the cloud. There are a few points in here that aren’t quite accurate that I thought might be worth correcting for other readers:
    - Route 53 is not an image of the root DNS system. It is a global service, but not related to how the DNS root servers are distributed globally.
    - DNS latency occurs both in propagating the change throughout Route 53 and throughout caching resolvers.
    - Route 53 is not AWS-specific and can be used with both AWS and non-AWS endpoints.
    - The nameservers assigned for a hosted zone are unique to that hosted zone. However, they are not dependent on where the customer is located.