Forum Discussion
DKIM selector1 record missing at 365
I didn't mention that I've changed nothing and this has suddenly affected twenty tenants in the last week (or thereabouts).
That seems set already as I'd expect. (Doesn't appear in Get-'s output.)
@@PS C:\Users\AlanMcFarlane\Documents\Temp> set-DkimSigningConfig -Identity XXndeesen.org -PublishTxtRecords
WARNING: The command completed successfully but no settings of 'XXndeesen.org' have been modified.
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
VasilMichev have noticed the same thing with our tenant. Lots of our domains Selector1 stopped resovling, but selector2 works. Seems to be a big problem on the Microsoft side. I have a support case, and if I can get past Tier 2 and talk to somebody who actually understands the problem, hopefully Microsoft will fix it because I don't want to script having to do this for the high number of domains I have.
- 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. :-,)- 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
PierfishMicrosoft
but you have changed the certificate with this. that's why you have a new record published.
