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.
Dee Bee commented
Alias records work great to support Apex (Naked) domains until you get to more than 20 redirects. You may ask why does one need to support more than 20 naked domains on one traffic manager profile? Answer: A web server hosting more than 20 domains. I have two ISP's servicing my facility and use traffic manager's priority endpoints to route traffic to whatever ISP is up. Works great until you exceed the maximum number of records that a Azure DNS record set can have. For Alias record sets, this limit needs to be reviewed and substantially increased. Creating a duplicate Traffic Manager for the second set of 20 aliases is a waste of resources.
Ivan Stoev commented
Jesus, can Azure implement alias records like Amazon does I've spent my whole day trying to figure out how to simply map my apex domain to a CDN endpoint which I created in Azure, its silly that you can map CNAME like www.mydomain => cdn.azureedge.net, but not be able to map the apex domain domain.com => cdn.azureedge.net like seriously Microsoft stop trolling and fix this issue already Amazon is like got this covered ages ago!
Tried new alias records but can't point at geographic traffic manager profile, get error
"Failed to create record set '@'. Error: RecordSets of type A or AAAA must reference a traffic manager profile with endpoints containing valid IP addresses"
What is recommended approach here? Thanks
Please move this up on the radar. We need apex domains to work with traffic manager to avoid issues during failover when I hit apex domain during failover, the redirect doesnt work because the first node is down
Jason Vickers commented
This is desperately needed as we have no reliable way to provide redundancy to clients that need support for apex domains. What is the status?
Sam Cofer commented
Where is this roadmap? has this feature been supported yet?
Yes, and the option to replace ***.trafficmanager.net as the endpoint by ***.yourowndomain.com - especially if your DNS is delegated to Azure.
I would like to know the status of this feature and when it is planned to be released! please! thanks again for such a great Azure product.
where can we find this roadmap? would like to know when this will be implemented
MS as requested already please can you provide estimates as to when traffic managers are likely to support apex records so it can provided solutions such as load balanced resilient 301 redirection.
Looking at the comments here they are going back 3 years+ so would be good to get an idea as to when this might be available as it's a much needed feature.
I'm glad to see that this is in the roadmap! Any more info about when it might be available? Are we talking "Q3", "2H2018"..."2019"?
GΛVĪN J commented
+1 on this requirement.
I'm currently using Cloudflare's CNAME Flattening functionality to return an A record in place of a "virtual" CNAME record for the zone apex, but this completely bypasses Traffic Manager, directing all traffic for the apex at a singular web app cluster thereby completely negating the benefit of globally distributing load at the DNS level.
Walsh. Stephen (Enterprise Services) commented
This is something we desperately need. Please can we have an update on this feature?
Rob Hudson commented
I support this effort. Please keep us posted!
Tom Wilson commented
Any update on this?
Jason Carter commented
We need this as well, hopefully they hit this KEY ROADMAP item soon.
any updates? This is a deal breaker for many people moving their websites to azure
Kevin Soule commented
Any update? We are wanting to use Traffic Manager, Application Gateway, Azure DNS, and Load Balancers as described in your other articles but this seems to be a road block.
Please consider adding this asap.
Any news on this feature?
This constraint has considerable influence on other Micorosoft Online services already.
I don't have all day. hurry hurry hurry hurry hurry up please!!