Azure DNS needs DNSSEC support
DNSSEC is required to be able to secure your DNS requests. At the moment this is not available. We cannot move until our domains to Azure DNS untill these requirements have been met.
Anonymous
shared this idea
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.
143 comments
-
Martijn Vandevyvere
commented
+1 for dnssec
-
Anonymous
commented
DNSSEC needed!
-
Anonymous
commented
Need DNSSEC for fedramp requirements, please add to short term backlog!
-
Anonymous
commented
Without DNSSEC there's no SSHFP or TLSA.
-
Anonymous
commented
We need DNSSEC too
-
Anonymous
commented
+1 for dnssec - it's a must in govermental setup in Denmark in a short time
-
Anonymous
commented
DNSSEC is pretty much getting a standard and best practise. It's about time it comes on the short-term roadmap.
-
Anonymous
commented
+1 to prioritize immediately--this is Security 101
-
Rajiv Gomer
commented
DNSSEC is essential! It's been over 3.5 years of being on the "long-term roadmap". Just how long term is this road? Customers are wanting to be fully in the MS Stack without needing 3rd party solutions to simple problems.
-
Paul
commented
DNSSEC is becoming a must have and it would be great to have this option in Azure DNS. Please re-evaluate the priority of this request and implement it as soon as possible.
-
Gagnon Martin
commented
Hello product manager. Could you please provide an update on the expected delivery date for DNSSEC Support. It has become a requirement from the security department of our company. I'd rather not have to migrate to a 3rd party provider.
-
Anonymous
commented
DNSSEC is one of the things security rating companies mark down an organizations risk score because of; this should make it a high priority.
-
Fred
commented
How on earth can you not prioritize this critical feature?
-
Anonymous
commented
This is a major issue!
-
Tom van der Wal
commented
Please reconsider the priority. Yes it is a large engineering effort, however this is becoming an issue that is preventing further growth. Even just missing the option prevents clients from moving to Azure DNS.
I know you know this, but just wanted to emphasize it / get it top of mind. -
Gustavo Lara
commented
This is a MUST HAVE feature for Azure DNS.
-
Anonymous
commented
Province of Drenthe needs this, considering the Government standards, look at:
https://www.forumstandaardisatie.nl/open-standaarden/lijst/verplicht
and
https://www.forumstandaardisatie.nl/sites/bfs/files/Lijst_verplichte_open_standaarden_sept-2018_0.pdf -
Håkon Klausen
commented
We are considering moving dns hosting to Azure to heighten security and ease integration with automations tools, but the lack of DNSSEQ makes it harder to argument for the change.
-
Anonymous
commented
+1 for dnssec
-
John Ashby
commented
DNSSEC needs to be a high priority. It prohibits the centralization of core services to the Azure cloud as security measures are not met for our company internally; or our customers externally.