CNAMES for Cloud Files
Cloud Files support for DNS CNAMES
The title says it all :)
Exciting news! Support for CNAMEs has been released. See this blog post for more information:
CFP Solutions commented
Here is an announcement in cartoon form
@acgann I believe it's OR at this time. Very few (if any) low cost CDNs provide SSL AND CNAMES. GoGrid charges $600/month with a $600 setup fee for that type of service (on top of your usage charges), limelight is $300/month with a $1k - $3k setup fee (also in addition to usage). Cloudfront is OR as well. If you need AND, look to the other providers.
Ok, so cnames AND ssl....OR....cnames OR ssl? This matters kids....no ssl with cnames and it's basically worthless to us.
Rackspace u awesome!!!
David Overcash commented
Any chance you'll support CNAME bandwidth reporting? It's pretty standard for most CDNs, and I have a feeling you could just proxy the APIs provided by Akamai.
Chris Garver commented
We're now in Q2. When can we expect this? It will impact the launch of a product we're developing...
Joshua Martens commented
I would love to have CNAMES for my cloud files. I vote a big fat YES to this!
bus bench commented
Still waiting... it'd be nice to have a schedule so we could know when to expect CNAME functionality to come rolling in.
Hasitha Prabath commented
Brian Gallagher commented
I can't help with the first two, but I just set up my FixSSL.com service here on my Cloud Sites server (just launched it this week) that will let you do the SSL portion.
Q2? So hopefully by June this year? I see this "feature" has been on the request list for months now already. Odd that something so important would be put on hold for so long. Oh, well, Amazon it is then.
Rackspace has announced its partnership with Akamai Technologies this morning. We plan to get you CNAMEs in Q2 of this year. Learn more on our blog...
I'm open for questions...
Can we at least get an explanation why this is not yet implemented? We need this!!!
Looks like MediaTemple just launched their ProCDN service. It's a little more expensive for smaller sites (flat $20/mo. fee for 200GB of bandwidth), but they offer CNAMES out of the gate. Might be worth a look.
This is what's keeping me from using RS
+1 ... really would like this...
Rackspace, you're awesome. I know you can do it! Go team!
kelly XR commented
without cname support we can't use the rackspace cdn. we'd like to. we like rackspace and have our physical servers here. but we're connecting them to amazon s3 right now. I have two sites which are growing and we'd like to use the rackspace cdn for them instead. but if this goes past jan 31, 2011. we will support their increased traffic by using amazon instead. Rackspace seems to really be snoozing on this feature.
Get on the ball rackers! Your income will increase if you make this work. Cause a lot of us would rather use you. your support is great. but your technical limitations (seems odd to say that in connection with rackspace) are holding you back .. and your customers back.
Stephen - if it was that easy do you think we'd all be on here bleating? :) Try it yourself, it doesn't work. Rackspace checks the referral cname:
HTTP request sent, awaiting response... 400 Bad Request
03:57:51 ERROR 400: Bad Request.
John LeBlanc commented
"We are working very hard to bring this feature to market for you."
Perhaps an engineer could take 2 minutes to write a quick blog post explaining why this is so difficult to implement?
Even though many competitors have already solved this, Rackspace customers might be more patient if we had any insight into the technical issues at hand.