My portal have multiple cname record, all point to same server. Like aaa.com, bbb.com and alson *.abc.com. I need this url in my web application to give proper content.

Now I want move Amazon Load Balancing.

  • How about my all cname records? Is there any road blocks?
  • When I use load balancer the user entered url aaa.com will posted to server or load balancer dns will posted to server?
  • Finally, is there any good articles about amazon load balancer.

2 Answers 2


Elastic Load Balancing gives you a CNAME as an endpoint. Here's an example:

$ host www.foursquare.com
www.foursquare.com is an alias for star-foursquare-com-367497865.us-east-1.elb.amazonaws.com.

As you can see, ELB works by providing a .wherever.elb.amazonaws.com domain name, with a low TTL. Amazon will then return you different DNS values for the ELB based on where you are coming from, and what backend servers are up. (I wrote a blog post on this topic once which I encourage you to read if you want more detail.)

So, you can make site.abc.com or even *.abc.com a CNAME to your .wherever.elb.amazonaws.com address, and the name will be forwarded to the instances behind it as you would expect.

aaa.com is trickier, as the zone apex (root name) cannot generally be a CNAME. The previous workaround was to point aaa.com to a single EC2 instance on an elastic IP, which you would re-map in the case of failure; however, Amazon recently released an addition to their Route 53 DNS service where they will set keep the DNS records for aaa.com in sync with what your ELB CNAME will return.

  • thanks a lot crb. I manage dns on dyndns.when i try to change dns record of *.test.aaa.com on dyndns it didn't accept xxx-load-balancer-5866547899.eu-west-2.elb.amazonaws.com, it looks for ip address. what about it.?
    – gandil
    Jul 13, 2011 at 10:26
  • Not everyone supports wildcard CNAME records. See serverfault.com/questions/44618/….
    – crb
    Jul 13, 2011 at 17:42

It should work fine with CNAME records. The browser simply keeps resolving until it gets an IP address answer, then sends a HTTP request with a Host header to that IP. AWS load balancers will just pass the Host header to the back-end webservers, which gives you regular Name-based virtual hosting functionality that you already use.

About good articles, have you tried Google? I'm kidding, but that question is far to general. Amazon has good articles and there are plenty of articles online.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .