|
Discussion Forums
|
Thread: ELB CNAME
 |
This question is answered.
Helpful answers available: 2.
Correct answers available: 1.
|
|
|
|
Replies:
58
-
Pages:
4
[
1
2
3
4
| Next
]
-
Last Post:
Jan 18, 2010 5:34 PM
by: andersvinther
|
|
|
Posts:
7
Registered:
3/29/09
|
|
|
|
ELB CNAME
Posted:
May 18, 2009 10:13 AM PDT
|
|
|
So ELB gives us a CNAME that we can point our domain name to.
However, I want to point the root of my domain to this - unless I'm mistaken you can't have a CNAME on the root of a record?
I have access to the the zone bind file - what should the syntax be?
www 10800 IN CNAME socialmod.com.
@ 10800 IN A 1.1.1.1
@ 10800 IN CNAME default-173007695.us-east-1.elb.amazonaws.com.
The above isn't valid (with and without the A record)
|
|
Posts:
2,027
Registered:
3/15/06
|
|
|
|
Re: ELB CNAME
Posted:
May 18, 2009 10:29 AM PDT
in response to: leadthink
|
|
|
You're right. At the moment, you can't do that. That was a topic of considerable debate in the private beta. I think that feature might show up someday (don't ask me when, I have no idea) but it's not there now.
Mitch
|
|
Posts:
7
Registered:
3/29/09
|
|
|
|
Re: ELB CNAME
Posted:
May 18, 2009 10:33 AM PDT
in response to: M. Garnaat
|
|
|
So I should just redirect everyone to a subdomain?
I think this is a fairly important (indeed critical) feature - I imagine most people will be in the same boat.
|
|
Posts:
2,027
Registered:
3/15/06
|
|
|
|
Re: ELB CNAME
Posted:
May 18, 2009 10:41 AM PDT
in response to: leadthink
|
|
|
I agree. This forces you to use a subdomain which is definitely not optimal. I hope that feature is high on the list. The best way to get it high on the list is to tell AWS it's important to you.
Mitch
|
|
Posts:
111
Registered:
7/21/08
|
|
|
|
Re: ELB CNAME
Posted:
May 18, 2009 10:48 AM PDT
in response to: M. Garnaat
|
|
|
I had forgotten that you can't have the root record of a domain be a CNAME. Wow, that is a deal breaker for one possible application of ELBs we were investigating.
-- Don
|
|
Posts:
1,134
Registered:
7/7/07
|
|
|
|
Re: ELB CNAME
Posted:
May 18, 2009 12:00 PM PDT
in response to: M. Garnaat
|
|
|
Using Elastic Load Balancer with a root domain name is important to me.
Many of my web sites like
http://alestic.com use the base domain name and I won't be changing this aspect of the brand to use a particular infrastructure. And, for the ones which use subdomains, I would like to use the same Elastic Load Balancer architecture to let web servers redirect, say,
http://campusexplorer.com to
http://www.campusexplorer.com
I also need to to be able to assign dynamic subdomains to the Elastic Load Balancer, as in *.notlong.com. I'm not sure if this can be done with CNAME.
|
|
Posts:
83
Registered:
11/16/07
|
|
|
|
Re: ELB CNAME
Posted:
May 18, 2009 12:32 PM PDT
in response to: leadthink
|
|
|
Hmm, I tested using the IP of the domain name provided and it works on that level, but I guess we have to assume that the IP can change at any time?
That would very much suck.
Frankly without having a set IP we can point to, you really can't use this for front end load balancing because of the origin CNAME DNS issue.
|
|
Posts:
12
Registered:
4/21/09
|
|
|
|
Re: ELB CNAME
Posted:
May 20, 2009 10:01 AM PDT
in response to: leadthink
|
|
|
We are working on a solution for this feature as our next highest priority item. We expect to be able to say something about delivering this, soon.
Thanks.
|
|
Posts:
83
Registered:
11/16/07
|
|
|
|
Re: ELB CNAME
Posted:
May 20, 2009 10:16 AM PDT
in response to: Ranjeet@AWS
|
|
|
Awesome, thanks for the update Ranjeet. I think ELB is a huge win for serious work in EC2, it's just that this whole root domain name issue is going to be an issue for a lot of people.
|
|
Posts:
252
Registered:
7/23/08
|
|
|
|
Re: ELB CNAME: Kill two birds with one stone
Posted:
May 20, 2009 10:25 AM PDT
in response to: Ranjeet@AWS
|
|
|
We are working on a solution for this feature as our next highest priority item. We expect to be able to say something about delivering this, soon.
I don't know what you were thinking about in terms of potential solutions, but you could kill two birds with one stone if you allowed customers to map an Elastic IP to an ELB, which is another requested feature.
It would allow customers to create an A record for their base domain to the EIP, and it would also allow customers to migrate easily between load-balanced hosting and instance-based hosting--two birds with one stone.
|
|
Posts:
1,134
Registered:
7/7/07
|
|
|
|
Re: ELB CNAME: Kill two birds with one stone
Posted:
May 20, 2009 12:39 PM PDT
in response to: Lenny
|
|
|
Another way to kill two birds with one stone would be for AWS to support hosting our DNS for us. Then all this CNAME redirection would not be needed and AWS could directly return the correct IP address based on internal rules.
We're already trusting Amazon's DNS with the CNAME, so might as well turn the whole thing over to them.
|
|
Posts:
130
Registered:
5/2/06
|
|
|
|
Re: ELB CNAME: Kill two birds with one stone
Posted:
May 20, 2009 3:57 PM PDT
in response to: Eric Hammond
|
|
|
> Another way to kill two birds with one stone would be for AWS to support hosting our DNS for us.
+1: As Eric and many other folks involved with the private beta for ELB are already keenly aware, the inability to use CNAME's with the zone apex is something I see as a /HUGE/ issue that needs resolution before a lot of folks, including myself, will be able to use ELB as their primary front facing interface into EC2. While getting /any/ solution in place is most important, an AWS-based DNS service is what I see as the most logical solution to a lot of problems, including this one.
Plus, you have to admit that "Elastic DNS" is such a cool sounding name that to not have it be an AWS-hosted service would almost be a crime. ;-)
|
|
Posts:
83
Registered:
11/16/07
|
|
|
|
Re: ELB CNAME: Kill two birds with one stone
Posted:
May 21, 2009 12:30 PM PDT
in response to: Eric Hammond
|
|
|
Elastic DNS would kill 3 birds if we could do PTR records with it.
|
|
Posts:
70
Registered:
5/14/06
|
|
|
|
Re: ELB CNAME: Kill two birds with one stone
Posted:
May 28, 2009 12:55 PM PDT
in response to: Mark A Mealman
|
|
|
Through the correspondence in this thread, we've identified several use cases for the Elastic Load Balancing service:
1. Using the load balancer for a subdomain (subdomain.mydomain.com):
This is the simple case. Set up a CNAME record that maps the load balancer DNS name to "subdomain.mydomain.com".
2. Using the load balancer for dynamic subdomains (<anything>.mydomain.com):
As specified in RFC 4592 (
http://www.rfc-archive.org/getrfc.php?rfc=4592&tag=The-Role-of-Wildcards-in-the-Domain-Name-System),it is valid to use wildcards in CNAMES. Therefore, you can setup dynamic subdomains by configuring a wildcard CNAME record that maps the load balancer DNS name to "*.mydomain.com".
3. Using the load balancer for the root domain (mydomain.com):
CNAMEs are not allowed on the root apex. We have received several requests for supporting this use case, and we are investigating ways in which we could enable it. We do not have a firm date on when we will support it. Meanwhile, given the CNAME limitation, here is a work around that would enable you to use the Elastic Load Balancing service with root domain names.
(i) Configure the root domain to a service that redirects mydomain.com to www.mydomain.com (or any other subdomain of your choice)
(ii) Similar to (1), set up a CNAME record that maps the load balancer DNS name to "www.mydomain.com".
|
|
Posts:
7
Registered:
9/24/08
|
|
|
|
Re: ELB CNAME: Kill two birds with one stone
Posted:
Jun 13, 2009 2:07 AM PDT
in response to: Ameet@AWS
|
|
|
Hi,
Any estimation on when a solution would be available?
I am mostly interested in the ability to have any subdomain linked to the load balancer and it seems my dns provider does not support this.
Thanks,
|
|
|
|
Sign in to the AWS Management Console
Create an AWS Account
