DKIM-DNS server

Hi @Tina Fraser, 

I hope you are doing well. 

As mentioned in the message from your CRM provider, the DKIM record has already been created on their side. The remaining step needs to be completed with your email or domain provider, as DKIM records must be published directly in your domain’s DNS.

To move toward a resolution, I suggest the following steps:

1. Confirm where your domain’s DNS is hosted (for example: Microsoft 365, Google Workspace, GoDaddy, Cloudflare, etc.).
2. Sign in to your DNS provider’s management portal.
3. Add the DKIM record exactly as provided by your CRM (including record type, host/name, and value).
4. Save the changes and allow time for DNS propagation (this can take anywhere from a few minutes up to 24 hours).
5. Once the DNS update has propagated, return to the CRM platform and complete the DKIM verification.

For more information, please refer to these documents:

• How to use DKIM for email in your custom domain - Microsoft Defender for Office 365 | Microsoft Lea…
• Connect your domain by adding DNS records - Microsoft 365 admin | Microsoft Learn

I hope you found the answer helpful, and I would greatly appreciate it if you could mark it as accepted. This helps highlight the solution for others who may be searching for similar information in the community. Your contribution not only supports fellow users in finding the right guidance more quickly, but also helps build a more resourceful and collaborative space for everyone. 

Thank you for your kindness and contributions to the forum.   

If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.     

To add the DKIM record from the CRM to the DNS server for an email domain used with Outlook/Microsoft 365, the DKIM values provided by the CRM must be added as CNAME (or TXT, depending on what the CRM gave) records at the domain’s DNS host.

For a Microsoft 365–hosted domain, the recommended approach is:

1. Sign in to the Microsoft 365 admin center.
2. Go to Settings → Domains.
3. Select the custom domain used for email.
4. Select DNS records → Manage DNS.
5. In a separate window, open the CRM’s DKIM configuration page and copy the DKIM host names and target values it generated.
6. In Manage DNS, add the DKIM records as provided by the CRM. Typically, they look like:
   • Type: CNAME
   • Host name (or Alias): something like selector1._domainkey (or whatever the CRM specifies)
   • Points to address (Target): the DKIM target value from the CRM
   • TTL: 3600 seconds (1 hour) or the default Repeat for selector2._domainkey if a second selector is provided.

If the domain’s DNS is hosted somewhere else (for example, GoDaddy, Cloudflare, or another registrar), sign in to that provider’s DNS management portal instead and create the same CNAME (or TXT) records there, using the exact host and value the CRM supplied.

After saving the records, allow time for DNS propagation (can be up to 24 hours). Then, in the CRM’s DKIM or domain-authentication settings, run its verification/check step so it can confirm the DKIM DNS records are present.

If Microsoft 365 is also sending mail for the same domain, ensure that its own DKIM/SPF setup is also configured as described in the Microsoft 365 admin center under Domains → DNS records → DomainKeys Identified Mail (DKIM) and SPF TXT record.

References:

• Connect your domain by adding DNS records
• Best practices for email marketing
• Troubleshoot domain authentication errors
• Authenticate your domains
• Email authentication in cloud organizations