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.
129 comments
-
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.
-
Boom, Erik
commented
+1 for DNSSEC
-
Jag
commented
not having DNSSEC is definitely a show stopper
-
Subodh Patil
commented
Why Azure is asking to move to the third party, instead they should implement this. If we move to the third party why to come back to Azure DNS? :)
-
Nitin Patil
commented
+1
We have an Azure customer (IT/ITES) who is certifying for FEDRamp. DNSSec is a red flag their audits have raised. DNSSec is a must have feature for them. -
Casper
commented
It is for lack of this feature alone that we will need to migrate away from Azure DNS. It is simply too important of a feature not to be a part of an enterprise solution.
-
Anonymous
commented
+1 for DNSSEC
-
William Parry
commented
What’s taking so long?
-
mikeb
commented
+1 for DNSSEC
-
Anonymous
commented
Yes, required against fraud forged dns
-
Scott Chapman
commented
DNSSEC is required for FedRAMP control SC-20 (according to the FedRAMP PMO)
-
Aleksander Pawlak
commented
3 years passed, please make sure we receive what we request for!
-
Anonymous
commented
+1 yes
-
Anonymous
commented
+1 for DNSSEC. surprised it is not there yet.
-
Mark
commented
+1 for DNSSEC support! (Dutch government, mandatory requirement for specific projects)