DKIM verification failing for more than two days.

Admin NaT 0

The custom domain DKIM and DKIM2 keep failing to verify for more than two days. Screenshot 2024-01-19 at 7.19.38 AM

brtrach-MSFT 15,791 Reputation points Microsoft Employee

2024-01-20T03:32:48.6433333+00:00

@Admin NaT We could use some more information to best assist you. Can you share the status that is shown in your screenshot? The status is truncated in your screenshot so it's difficult to understand what is happening here. Next, what steps did you take to prepare/setup for this? We want to ensure you followed the proper steps before starting the procedure. We look forward to your reply.
Admin NaT 0 Reputation points

2024-01-20T03:43:39.06+00:00

The status for these two columns do not change to 'Verified'. I tried many times in last two days.
The SPF, DKIM and DKIM2 configurations are on one page. While, SPF status is 'Verified' for more than two days, the other two keeps changing to 'Configure' or stays 'Verification in progress'.
Admin NaT 0 Reputation points

2024-01-20T03:44:44.0733333+00:00
Ebraheem Al-Muneyeer (MSFT) 951 Reputation points Microsoft Employee

2024-01-21T15:04:59.8566667+00:00

@Admin NaT , It seems you are trying to configure a subdomain under your domain. If this is the case, please check the following documentation https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/email/add-custom-verified-domains#configure-sender-authentication-for-custom-domain, you need to modify the DKIM value by adding the subdomain as mentioned in the examples.

It will be great if you can share with us the hierarchy of the domain you are trying to add, and if you are trying to add the DKIM into the root domain or subdomain
Admin NaT 0 Reputation points

2024-01-21T17:11:35.47+00:00

Hi, I am following the instructions from the page you shared in the comment above. I want to add the record to root domain and not subdomain. The instructions had 'notifications' so I used it. Please guide how to configure DKIM and DKIM2 for root domain. Thanks!
Ebraheem Al-Muneyeer (MSFT) 951 Reputation points Microsoft Employee

2024-01-22T06:23:14.35+00:00

I'm not sure what is the hierarchy of your domain, but let's assume you are trying to add notification.azurecommtest.net subdomain and you are adding the DKIM records in the azurecommtest.net domain, so, you need to modify the DKIM name to be: selector1-azurecomm-prod-net._domainkey.notification
Ebraheem Al-Muneyeer (MSFT) 951 Reputation points Microsoft Employee

2024-01-22T06:26:42.29+00:00

I'm not sure what the hierarchy of your domain looks like, but let's assume you are trying to verify notification.azurecommtest.net subdomain, and that you are adding the DKIM to the azurecommtest.net domain, then you need to modify the DKIM name by adding the subdomain, so in the above example it should look like the following: selector1-azurecomm-prod-net._domainkey.notification
Admin NaT 0 Reputation points

2024-01-23T16:22:22.53+00:00

Hi, I don't have DNS zones. I tried that but it is not working. Can you share sample records for SPF, DKIM and DKIM2 for example domain name abcdefg.com?
Ebraheem Al-Muneyeer (MSFT) 951 Reputation points Microsoft Employee

2024-01-24T07:41:06.34+00:00

If you are verifying domain abcdefg.com, then there should be no changes on the SPF, DKIM and DKIM2 records, you just need to copy them from the Azure portal as is.

Your domain in the screenshot appears like notifications.something, which sounds like a subdomain. If you still have issues with this, is it possible for you to open a support ticket, so someone can view your setup, otherwise, please put here what is the domain you are trying to add, and where you are adding the DKIM records on which level. You can come with a dummy value for the domain if you wish, but please make sure to maintain the hierarchy.
brtrach-MSFT 15,791 Reputation points Microsoft Employee

2024-02-05T01:49:21.7233333+00:00

@Admin NaT Please let us know if you have an update to Ebraheem's previous question. We look forward to your reply.

Share via

DKIM verification failing for more than two days.