Forum Discussion
Not Able to enable DKIM in Office365 - Online Exchange server
- Aug 22, 2020
Hey Sumesh1980 ,
Okay, Just tested it, it appears you did not run the command :
New-DkimSigningConfig -DomainName <domain> -Enabled $false before updating the CNAME records.
So here are the steps that you need to complete in order to get this working:
1. New-DkimSigningConfig -DomainName <domain> -Enabled $false
2. Get-DkimSigningConfig -Identity <domain> | Format-List Selector1CNAME, Selector2CNAMEGrab the CNAMES and update them in DNS.
Then run the command:
Set-DkimSigningConfig -Identity <domain> -Enabled $true
After running the command in Step 1, it should not give you the domain not found error.
Thanks
Hey Sumesh1980 ,
Okay, Just tested it, it appears you did not run the command :
New-DkimSigningConfig -DomainName <domain> -Enabled $false before updating the CNAME records.
So here are the steps that you need to complete in order to get this working:
1. New-DkimSigningConfig -DomainName <domain> -Enabled $false
2. Get-DkimSigningConfig -Identity <domain> | Format-List Selector1CNAME, Selector2CNAME
Grab the CNAMES and update them in DNS.
Then run the command:
Set-DkimSigningConfig -Identity <domain> -Enabled $true
After running the command in Step 1, it should not give you the domain not found error.
Thanks
- harveer singhAug 22, 2020Iron Contributor
It depends on the DNS you are using and there may be a delay but most of the times it is not actually the DNS rather incorrectly updated records. The common mistake is to end up updating domain name twice like for example :
selector1._domainkey.domain.com.domain.com is updated as the CNAME instead of simply selector1._domainkey.domain.com.
Please follow instructions related to your DNS provider only to update the records. See this case in older post:
https://techcommunity.microsoft.com/t5/exchange/unable-to-activate-dkim/m-p/1540512
Thanks
- Sumesh1980Aug 23, 2020Copper Contributor