SES DKIM verification pending for autodba.co despite public DKIM CNAME records resolving

Question

I am trying to verify autodba.co for Amazon SES in us-east-2.

The SES identity previously failed after 3 days with AWS_SES_DKIM_PENDING_TO_FAILED. I retried/recreated the identity,
  and SES generated the same 3 DKIM CNAME records. The identity is now pending again.

All 3 DKIM CNAME records are published in Cloudflare, set to DNS only, and publicly resolve correctly. MXToolbox
  confirms DNS Record Published for all 3 records.

Domain: autodba.co
  Region: us-east-2

Could someone help explain why SES is not verifying DKIM even though the CNAME records are publicly visible?

Riku_Kobayashi · Answer

Hello.

Is it possible to share specific domain records or values?  
I think you need to check if there are any discrepancies between the CNAME record issued by Amazon SES and the record registered with Cloudflare.  
If name resolution is working using commands like `dig`, you need to check the record content for any errors (typos, etc.).  
I have also set up records in Cloudflare's DNS in the past, but simply copying the CNAME record issued by Amazon SES didn't work.  
I was able to make it work by registering the "hoge_domainkey" part in the Name field.  
In other words, I'm concerned about whether I'm accidentally registering unnecessary parts along with the record.  
https://isala.me/blog/free-custom-email-aws-ses-cloudflare/#:~:text=Via%20Cloudflare%20Dashboard%3A

SES DKIM verification pending for autodba.co despite public DKIM CNAME records resolving

Add your answer

Relevant content