CODEWITHSUNDEEP
azurednsazure-web-app-service
Oliver Weichhold
Oliver Weichhold

Reputation: 10296

Naked domain support for Azure Websites

From the looks of it the new Azure Websites Feature still does not support hosting them under a naked domain such as example.com instead of www.example.com. Am I missing something?

Upvotes: 6

Views: 4569

Answers (4)

Joe Healy
Joe Healy

Reputation: 5817

The conversations above are a bit dated. This entry however, comes up at the top of the list when folks are hunting/searching for Azure Naked Domain support.I'd update the answer.

Azure now supplies an IP in shared and > plans, and you can configure a naked domain.

Check out the following articles for more info:

Upvotes: 3

Christofer Eliasson
Christofer Eliasson

Reputation: 33865

Azure Websites have now released support for naked domains. Websites that are run on Shared or Reserved instances does support naked domains through an A record. Domain management is available through the Azure management portal.

Update 2012-10-21:

I previously stated that free instances could rely on CNAME to redirect a subdomain to their free Azure-website, but this appear to be incorrect, at least at the moment. Doing a CNAME to your Azure-website will result in an HTTP 404, as reported by MemeDeveloper in his comment.

However, if you run your website on a Free instance, you are still limited to CNAME, so for those websites naked domains are not possible.

Update:

As MemeDeveloper suggest in his comment, there are web services you can use that will take your naked-domain example.com and redirect it to www.example.com for you. For your www subdomain you could then have a CNAME to your Azure-URL.

Not as clean as a simple A record that is available for your paid websites, but a workaround for your free sites.

Upvotes: 4

Gleno
Gleno

Reputation: 16959

There seems to be some confusion about this. I don't know what the deal with Websites is, but normal Azure Web Roles provide a virtual IP address that is guaranteed not to change unless you delete a webrole deployment.

You can bind a domain name A-record to that VIP, as described here.

In practice, that means that when I want to update my website, I have to do a staging deployment first; and then switch it with the production deployment, and finally delete the staging deployment. The only caveat that I've been aware of, is that you can't do this if you switch your endpoint configuration (not even names).

I'm currently looking if there are same kinds of guarantees for websites, but haven't found appropriate documentation yet.

Upvotes: 0

tofcoder
tofcoder

Reputation: 2382

Azure does not support naked domain, because this requires to map definitively an IP address to the domain name. To map a naked domain name, you need a 1 record in the DNS. So, in this case, services like load balancing are more difficult to put in place.

Most registrars provide a way to redirect a naked domain request to another name, through HTTP redirect mechanism. For instance, you could redirect example.com to www.example.com.

Upvotes: 0

Related Questions