Forum Discussion

Alanjmcf's avatar
Alanjmcf
Brass Contributor
Jan 21, 2020

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...
exchange online
office 365
Pierfish's avatar
Pierfish
Icon for Microsoft rankMicrosoft
Jan 21, 2020

Alanjmcf 

 

use Set-DkimSigningConfig with -PublishTxtRecords

  • Alanjmcf's avatar
    Alanjmcf
    Brass Contributor
    Jan 21, 2020

    Pierfish 

    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.

     

    • VasilMichev's avatar
      VasilMichev
      MVP
      Jan 21, 2020

      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

      • JasonSCarter's avatar
        JasonSCarter
        Brass Contributor
        Jun 12, 2020

        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.

Resources