Provide a 301 (Permanent) redirect service for apex (naked) domains
Discussed in the Azure DNS docs: https://azure.microsoft.com/en-us/documentation/articles/dns-getstarted-create-recordset/#comment-2294403853
Right now, you must use a static IP address if you want to point an apex (naked) domain (e.g., mycompany.com) to a Cloud Service (e.g., mycloudservice.cloudapp.net). Static IP's are stable as long as the Cloud Service isn't deprovisioned; however, for maximum security, simplicity, and maintainability (i.e., even if a cloud service is deprovisioned), it would be awesome if we could have 301 redirects for the apex domain to a the www CNAME endpoint and not need to be concerned with the IP address of the Cloud Service at all. The scenario goes like this:
(1) The root domain (mycompany.com) should 301 (permanent) redirect to the www CNAME (www.mycompany.com)
(2) The www CNAME (www.mycompany.com) should direct to the Cloud Service endpoint (mycloudservice.clouadapp.net)
SEO would like that the best, as the 301 redirect would properly point traffic sources to the ONE endpoint we care about here (the 'www' endpoint).
We are evaluating this feature ask. However, it is not on our immediate roadmap.
Please add this feature!
Vincent Yim commented
@Azure networking team: Is your official response to now use the Azure Front Door service's URL redirect feature? https://docs.microsoft.com/en-us/azure/frontdoor/front-door-url-redirect
Sad we have been waiting for this feature so long and its being ignored. I guess customers are no longer the kings.
need this, currently have to do with an a function
AWS already has url forwarding supported utilizing DNS and S3. I guess we'll have to stick with utilizing AWS for our DNS.
Please add this feature, really basic requirement. Come on MS sort it.
Aaron Kelly commented
Please add this feature. Migrating to Azure DNS is our preferred choice, but with this limitation in place, it makes the decision more difficult when we can utilize other providers with this capability.
Ajit K commented
We can move our external DNS services to Azure if URL redirection is supported. Please add this feature.
Martin Meixger commented
for reference: 4 years later this is still needed and now with the new free "Managed Certificates" also for http[s] non-www to www:
+3 again been waiting on this for a couple of years so we can fully migrate to ADNS
Jeff M. commented
+1 for redirects
This should be quite simple to implement. This is obviously a commonly used feature that has been provided by other DNS providers for years.
I suppose this is what happens when MS decides to import 'talent' instead of using what is all around them...
+1 for redirects
L J commented
Please add the feature asap
While we don't offer a 301 redirect service, we just announced support for Alias records which will let you point to any Public IP-backed resource (such as Application Gateway) or a Traffic Manager profile, from your zone apex. This may be an alternative if the need is to make sure both the zone apex and say the www subdomain point to the same load balanced application. For more details see https://azure.microsoft.com/en-us/blog/announcing-alias-records-for-azure-dns/
this is a widely used feature that many DNS vendors provide. Reducing complexity of being able to do domain redirects to a URL is a critical feature that we have chosen when shopping for DNS service vendors.
Please introduce this feature soon.
Joshua Lloyd commented
2018, no updates from Azure yet.
Ludovik DOPIERALA commented
Need forwarding DNS to transfert DNS to Azure.
simple http web listner to a cname or a record
redirect 301 to new url
August 2017. A missing feature compared to some other prominent providers. Would be nice to have as a one for all solution rather than deploying resources elsewhere to accommodate.