Support apex (naked) domains more seamlessly
Some things work, other things don't. I can setup an apex domain, but to get SSL working on an apex domain in hosted cloud service web role requires tweaking. Traffic manager doesn't work with apex domains.
Azure needs a DNS service like Amazon's Route 53. (http://aws.amazon.com/route53/)
We just announced support for Alias records in Azure DNS public zones. See our blog post here: This is now available with Azure DNS in the form of support for Alias records. See our blog post here: https://azure.microsoft.com/en-us/blog/announcing-alias-records-for-azure-dns/
You can point to any Public IP-backed resource (such as AppGW) or a Traffic Manager profile (with external endpoints) from your apex (naked) domain.
Rhys Harris commented
Is there any updates on this? This is the biggest show stopper for many people wanting to move websites to Azure.
Eric Resnick commented
Azure will finally compete and surpass AWS if they add this. And they will fail utterly if they don't.
Please add public IP support to Traffic Manager so we can use A-records to point to Traffic Manager. This is the biggest show stopper for large scale websites in Azure.
I need to point my naked domain to the same CNAME address the www versio is running ( from the cloud app service).. Something like the AMAZON route 53..
Its 2 years!? Come one.
Martin Costello commented
I just tried to migrate my site from 2 instances in one datacenter to one instance in two datacenters, and fell at the last hurdle when configuring my DNS to point to Traffic Manager.
My primary domain is the apex domain, so while Traffic Manager correctly routes requests to www, they all end up being redirected to the IP of one instance running in one datacenter due to the redirect from www to the apex domain.
In this configuration, I'm actually worse off than when I started!
Microsoft - Are we close on this one? Any news you guys can give us?
What is going on with this?! When will apex (naked) domains be supported?! I want to host some static websites but I can't do that using Azure until apex domains are supported. Until then I will be forced to use S3 and Route 53.
Please provide support to use Traffic Manager with apex/root/naked domains i.e. domain.com
CNAME is not an option on apex/root/naked domain
AWS provide a work around when using their Route 53 DNS service. Will this be included in the Azure DNS service which is currently in preview
Is there any progress on supporting naked domain names with traffic manager yet? It has been 18 months since the original request, so it would be good to get an update on what the team are thinking and whether this is something that will be undertaken.
Do we have some update on Naked (APEX) domains for Traffic Manager? This is causing additional costs to apply redirects and other workarounds to work.
Jimmy from Sydney commented
Has any progress been made on this feature of the utmost importance?
I crave to host my static web sites on Azure. I crave it so bad! But I also crave the use of my apex domain for these sites. I can't do "www." any longer. I just can't do it!
I don't want to use S3. My gosh, I want to use Azure! But until Azure supports naked domains better, I am stranded! I am a man who has no choice but to not use Azure. It makes me sad, and it makes me weep.