'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Microsoft 365 DKIM CNAME Records Not Detected at Crazy Domains
Question details
Microsoft 365 is unable to detect or validate DKIM CNAME records published through Crazy Domains.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Setting up email authentication by publishing selector1 and selector2 DKIM CNAME records in the DNS provider.
- Observed behavior
- DKIM validation fails for over two weeks despite the records appearing correct in the Crazy Domains administration portal.
Before making any DNS changes, use a public WHOIS or DNS lookup tool to verify which name servers are currently authoritative for your domain.
Update DKIM CNAME Records in the Active Authoritative DNS Provider
Use this solution if your domain name servers are pointing to a service other than your domain registrar, which prevents updates at the registrar from taking effect.
When domain name servers (NS) are pointed away from the original registrar (like Crazy Domains) to another provider (such as Microsoft 365), any DNS records added at the registrar will not be detected. You must apply the CNAME records to the active DNS host.
Use a DNS lookup tool (such as MXToolbox) to check the NS records for your domain. Confirm whether they point to Crazy Domains or Microsoft's name servers.
If the name servers point to Microsoft, log in to the Microsoft 365 Admin Center. If you intend to use Crazy Domains for DNS management, log in to the Crazy Domains portal and ensure your name servers are restored to their default values.
When creating the CNAME record, do not append your full domain name if the provider adds it automatically. Enter only 'selector1._domainkey' instead of 'selector1._domainkey.yourdomain.com'.
Save the new CNAME records in the active DNS zone. Wait for DNS propagation, then return to the Microsoft 365 Defender portal to re-run the DKIM validation.
Need a simpler way to manage your office work? Try WPS Office
While resolving complex Microsoft 365 DNS and admin policies, you can rely on WPS Office as a lightweight, free, and highly compatible alternative for all your document needs.
- 1. Download the installer: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install the software: Run the installer and follow the simple on-screen instructions to set up the software.
- 3. Open your Microsoft formats natively: Launch WPS Office and directly open your existing .docx, .xlsx, or .pptx files with full formatting retention.
Frequently Asked Questions
Why does Microsoft 365 fail to detect my DKIM records?
This commonly occurs if your domain's name servers point to a different DNS provider than where you added the records. For example, if you add records in Crazy Domains but your name servers point to Microsoft, the changes won't be detected.
Should I include my domain name in the DKIM selector field?
Usually, no. Most DNS management portals automatically append your root domain. If you enter 'selector1._domainkey.yourdomain.com', it may resolve incorrectly as 'selector1._domainkey.yourdomain.com.yourdomain.com'. Use just 'selector1._domainkey'.
How long does it take for DKIM CNAME records to propagate?
DNS propagation typically takes anywhere from 15 minutes to 48 hours depending on your TTL (Time To Live) settings and global DNS caching. If validation fails immediately, wait a few hours and try again.
