913 votes34 comments · Networking » Domain Name Service (DNS, Traffic Manager) · Flag idea as inappropriate… · Admin →
This remains on our long-term backlog as something we want to offer as part of the Azure DNS service in due course. Thank you everyone for the feedback so far, and please continue to share your comments.
+3, Any update??
We are adding this control to our CLI soon. In the meantime you can use the simple CLI commands outlined here: https://github.com/MicrosoftDocs/azure-docs/issues/27964
Those commands should be in the App Insights docs soon.
thanks for the feedback!
@Admin: Awesome! Looking forward to doing it via Azure cli 😉👍
Any update on this?
At this point our recommendation is to move resources into a new Resource Group with the new name.
App Service Environment's and probably other resources can't be moved they have to be re-deployed. So it still would be a very nice and needed feature
this feature has been postponed as it wouldn’t be complete and might be revisited later if standards/supported features by CAs and browsers change (double wildcard certificates are not supported standard, resulting in no way to secure double wildcard domain)
This is not an "Azure" feature and nothing that Azure should support by itself. This is the way SSL is defined in the RFC and the only way that can be changed is by changing the RFC.
Se this post for details:
The best way to support it would be to implement it at the right level so fx:
So use a dash, don't use subdomains.
In my opinion its never a good option to do a work around for bad user behavior. Instead of bending a system to support the wrong doing of users, we should all try and educate them into not typing "www." in front of stuff when not instructed to. Or send them a direct link instead.
Should we also add ".*" or ".com" to the certificate because users type ".com" in the end?
Let's say I have a domain with an app on it:
Should the certificates and Azure support "www.coolapp.mysite.dk.com" just because users are doing it wrong?
The option to manage your restrictions through PowerShell is on its way and the docs and being written to explain how to do this. We’ll update when the docs are out.
We are considering a update service but not specific plans right now. Thanks for the recommendation. Let’s get the votes up. :)
2,883 votes118 comments · Networking » Domain Name Service (DNS, Traffic Manager) · Flag idea as inappropriate… · Admin →
DNSSEC remains on our long term roadmap, however it is unlikely to be available in CY 2019. If DNSSEC is a critical and immediate requirement for your business we’d suggest that you consider evaluating 3rd party DNS hosting solutions that provide this feature.
Any update from Microsoft on this request? It's quite important for many companies and a showstopper for migrating to Azure DNS for many