I'm considering using a DNS solution to solve the issue with elastic IPs for Windows Azure roles. This blog post describes how to have both example.com and www.example.com point to an azure role such as example.cloudapp.net. However, I would like to streamline the process so that there is no forwarding.
One solution I've found is DNS Azure and another that seems to fulfill the requirements is Amazon Route 53. I was wondering whether anyone has had experience with either one of those for this particular task.
Best Answer
As long as you always have something deployed in Azure then your IP address will not change. We use A records on our DNS configuration to point to our IP address because it hasn't changed in the past few months.
New deploys either replace the existing deploy (thereby keeping the same virtual machines) or get deployed using a VIP swap (which keeps the same IP address).
If you want to you could also use CNAMES rather than A records. This takes care of keeping it up to date.