Forum Discussion
Can't Enable DKIM in Office 365
AOL, Yahoo, and Verizon (using the same email server) are now requiring that SPF, DKIM, and DMARC be enabled for emails sent to those addresses. I saw a report that Google will soon require this too...
You mentioned that DKIM was already enabled without CNAME resource records.
Activating requires two CNAME records in an external DNS zone of the M365 custom domain, not an internal DNS zone. EXO checks the availability of the correct CNAME records before activation of DKIM.
What do the mean by "4 accounts on 4 different providers"?
There should only be one name server provider for the DNS records of a custom domain.
May be I am getting this wrong.
-Thomas
I am a little confused with what I am seeing on the Defender admin page. There seems to be 2 domains, but the format is not consistent. My account shows my domain and another one that says NETORGxxxxxxx.onmicrosoft.com. Another account shows the domain and domainroot.onmicrosoft.com. Where domainroot is the domain name without the ".com" extension.
The selectors for my account have NETORGxxxxxxx embedded in the "points to".
The selectors for my account have NETORGxxxxxxx embedded in the "points to".
- I think my previous post got lost. I apologize if I posted 2 versions of the same comment.
I managed get 5 out of my 6 email domains working. The 6th is a problem. The DKIM flyout on the Microsoft Defender page show 2 entries. The first entry is the domain itself. The second entry is the domain root with onmicrosoft.com appended.
The flyout for the onmicrosoft.com entry reports that DKIM is enabled and that it was last checked on March 13, 2024 10:56.34 AM (today). The flyout for the entry with just the domain name reports That DKIM is disabled and was last checked on March 9, 2016 10:56.34 (8 yeas ago). I suspect that this lack of a check is why I can’t enable DKIM on this account. Is there a way to force an updated check of this DNS?