DNSSEC support in Office 365
Please add DNSSEC support for managed domains in Office 365 business (enterprise) plans
the dutch goverment has made DNSSec obligatory
Microsoft support, please have a look at this: https://internet.nl/mail/microsoft.com/235952/
Had contact with a Dutch sales representative for Office 365. He told me that DNSSEC was implemented. However (many hours later searching and calling with tech support....), it isn't implemented in any way. There are also no current plans to implement this in the future.
How can O365 boast about it's security but have this best-practice methods not available for it's customers?
R. Willems commented
Is there any update on this issue? We need to know if and when this feature is implemented.
DNSSEC and Dane are best-practise or at the least strongly adviced to be implemented.
Laba diena.Lukai gal gali pagelbeti man as buvau Office 365 pasidejas pinygus ir man ana paskira pavoge.Gal padetum susigrazinti paskira?
James Schmidt commented
Agreed - DNSSEC should no longer be an afterthought for MSFT but a 'P1' type issue.
David Rukavina commented
I logged a premier support case with MS asking about DANE for EOP, and got the following reply from the support technician today:
"I got the following update from the Engineering group PM for this area:
There are ongoing discussions with O365 Security about DANE, but right now there are no plans to support it."
Tomas Hala commented
Also include DANE, please.
John W. O'Brien commented
DNS-based attacks seem to be growing in sophistication, frequency, and persistence. ICANN recently called for full deployment of DNSSEC across all unsecured domain names, which, right now, includes the domains associated with Office365.
Microsoft: DNSSEC is not a feature. It is a fundamental, infrastructure security capability. You should not be asking your users to vote on it, but instead making immediate and concrete plans to roll it out just as you would the next version of TLS.
Alessandro Kornowski commented
2019 arrived and still nothing about DNSSEC? In some months this request will be on 3rd birthday and 0 return from microsoft??
Michael K commented
This requires DNSSEC to be enabled on the outlook.com domain, or to create a second secure domain, and migrate customers MX records to the second one. I cannot see the risk in the first, but if Microsoft are worried about a breaking change, then option 2 gives customers the option to secure their email environment.
Very strange that am Enterprise mailing service such as o365 is not implementing these standards. Disappointing
KH Eng commented
I so disappointed why Microsoft didn't take serious action again this feature as top priority. Security concern just let it on behind since December 01, 2016 19:53. Microsoft have world wide top professional within company but why can let this be happen!!!!! Please take immediately action for this enhance for upcoming feature add in.
Both DNSSEC and DANE would be something I'm looking for
Andy Marchand commented
Are there any news on this subject?
I do really have troubles with missing DNSSEC on .info domains, which are no longer accepted as e-mail senders by a growing number of important hosts like Gmail...
Henk Steenwijk commented
I'm actually quite surprised dnssec and Dane aren't yet supported, now we have to move the domain name to a different hosting provider to achieve the level of security we require. I always thought Microsoft was trying to create an all in one solution?
alfredo sanchez commented
i have problems to recibe some domains because DNSSEC not recognized my domain in Office365
Microsoft... time to implement this. It's not sufficient secure anno 2018 and all the years before this year.
Berrie Pelser commented
DNSSEC would be very nice to have, when do you think you can have this in?