Forum Discussion
DKIM selector1 record missing at 365
Anyone else seeing DNS failures resolving the selector1 TXT record supplied by EXO for each domain? selector2 is fine. I'm seeing that across my fleet of customer tenants. @@PS C:\Users\A...
I'm seeing the same behavior, and yeah haven't changed a thing here either. Best open a support case, I will ping few folks just as well.
For the record, I fixed it by running:
Rotate-DkimSigningConfig -Identity domain.com
I’ve sent a grand total of two emails from two tenants and both were sent with selector2. So after that huge test…hopefully the lack of selector1 isn’t breaking email delivery.
Maybe all tenants did a key rotation to selector2 and something stopped them creating selector1.
My experiences with support recently have been somewhat lacking (they don’t escalate clear issues etc) so reporting it here was my alternative. :-,)
Maybe all tenants did a key rotation to selector2 and something stopped them creating selector1.
My experiences with support recently have been somewhat lacking (they don’t escalate clear issues etc) so reporting it here was my alternative. :-,)
- From a quick check (from my iPhone) looks like the records are back — well for that one domain at least.
Just a wee blip I guess. But I also wonder why key rotation apparently happened for all domains at the same time. Maybe to do with https://www.microsoft.com/en-us/microsoft-365/roadmap?featureid=56752- I checked an hour or three ago and it is NOT fixed. The selector1 record is still missing except for those domains where I did the PowerShell command suggested by Pierfish That brings the record back to life — even though that option is already set to true.
Looks as if both records are back for all my tenants.
