Up until recently, hosting a load balanced site on Amazon AWS presented a problem – naked domains. The workaround I used in the past was to associate an elastic ip address to one of the EC2 instances, create an A record pointing to the elastic ip address, a CNAME (www) pointed to the load balancer, and then configure nginx on the EC2 instance with the associated elastic ip to route all naked domain requests to the load balancer. Not ideal.
This was the same solution I was using for Mistash until running into DNS issues with my provider a few weeks ago. The site stopped resolving properly and www.mistash.com was being directed to a parked page. Ugh. I put in a support ticket with the provider and decided to check out Route53.
Turns out that Route53 now supports aliasing for A records to the load balancer! I activated Route53 in my management console, moved over all the DNS info, and within 30 minutes everything was golden and the site was resolving properly again. Thumbs up!