AWS’ DNS offering, Route 53, is a great option for managing the basics of name resolution when resources exist solely within the AWS ecosystem. Route 53 integrates with most all of AWS’ services, offers great alias record functionality, and is easy to automate. However, for enterprises looking to make the move to AWS, especially in a hybrid deployment, Route 53 will most likely not be enough to provide all of the name resolution capabilities required. Because of this, hybrid DNS solutions need to be explored and implemented.
Through the rest of this post, I’ll explain some of the key areas to consider when planning your internal DNS strategy for moving to the cloud, as well as some learnings and challenges from previous DNS projects I’ve encountered. This post will focus on internal, private DNS zones.