1,996 votes73 comments · Networking » Domain Name Service (DNS, Traffic Manager) · Flag idea as inappropriate… · Admin →
Thanks for the suggestion. We recognise the strategic importance of DNSSEC and it is a key feature on our long-term backlog.
DNSSEC represents a very large engineering investment, and hence we have to prioritize carefully vs other work. The most customer data we can get supporting the need for DNSSEC support, the better prioritization decisions we can make. We appreciate your votes and your comments.
Thank you for your feedback. We are currently in public preview of static website hosting for Azure Storage to enable this scenario. Check out the blog post here for more details: https://azure.microsoft.com/en-us/blog/azure-storage-static-web-hosting-public-preview. The feature set includes support for default documents and custom error documents for HTTP status code 404.
For any further questions, or to discuss your specific scenario, send us an email at firstname.lastname@example.org.Darrell Enns commented
Why does this need to depend on custom SSL domain support? Even without SSL, it would still allow serving unencrypted content, serving https using the azure domain name, or serving HTTPS with custom domain names by chaining it through CDN.