Take the 2-minute tour ×
Webmasters Stack Exchange is a question and answer site for pro webmasters. It's 100% free, no registration required.

I'm experiencing some issues with a website I am working on, for a company called BlueSEQ. We recently switched to Windows Azure to get more scalability and performance, but we are having issues regarding the domains.

We would like blueseq.com to be the main domain instead of the current blueseqservice.cloudapp.net. Is that possible? I tried making an "A" record pointing to the "VIP" of the Windows Azure service, but whenever I republish the project to Azure, I get a new IP.

Any suggestions?

share|improve this question

migrated from superuser.com Aug 22 '11 at 4:19

This question came from our site for computer enthusiasts and power users.

    
Yes you can use A records now, as the IP is now retained across republishing. See my answer below for details. –  TrueBlueAussie Jan 5 '12 at 18:35

3 Answers 3

You need to create a cname record on your DNS host and forward it to blueseqservice.cloudapp.net. A cname behaves like an A record but rather than forwarding to an ip, it targets a fqdn.

share|improve this answer
1  
Note that for frustrating technical reasons you probably can't create a cname at blueseq.com. Instead you'll need to use www.blueseq.com . This sucks if you're going naked with your domains, but is a big limitation of cloud systems that use DNS load balancing. –  jcrawfordor Aug 22 '11 at 4:38

Apparently you can - Azure now supports A Records as it provides fixed IP addresses:

With an A record, you map a domain (e.g. contoso.com or www.contoso.com) or a wildcard domain (e.g. *.contoso.com) to the IP address of a deployment within a Windows Azure hosted service. Accordingly, the lifetime of this IP address is the lifetime of a deployment within your hosted service.

The IP address gets created the first time you deploy to an empty slot (either production or staging) in the hosted service and is retained by the slot until you delete the deployment from that slot.

See this link for more information - Section: Expose Your Application on a Custom Domain

Just tested it with one of my own domains and a sample Azure app in staging. - Works a treat!

I found when you use the Swap VIP option, to move from staging to production, your staging IP address gets taken with you. This meant I retained the staging website pointed at by my A record after republishing and after swapping to Production. The downside to this is that your domain points at staging or at production when you swap, which is probably not what you wanted as your domain would likely only point at production. A CNAME record will do that, but does not allow for a blank subdomain.

share|improve this answer
    
The link is broken. –  Mathias Lykkegaard Lorenzen Aug 5 '13 at 7:38
up vote 1 down vote accepted

Azure websites and Azure web services now offer A record support for domains as default. They didn't at the time of writing the original question.

That's a good thing!

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.