Question

Amazon SES not finding TXT DKIM in DNS section ?

  • Posted August 12, 2013

Title says it all; trying to verify my domain using the DNS settings in DigitalOcean and twice now, Amazon has failed to verify it

I have added the TXT and 3 CNAME values to the DNS record; I’ve tried with the _ in the TXT entry and without (as i’ve read elsewhere) and it continues to fail verification.

Any ideas?

Subscribe
Share

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hi - just to add to this thread. For TXT values Do add a period at the end of the key (post 1) Enclose Value in double quotes Add new TXT _amazonses.domain.co. “LOng+Key”

Strangely enough (for me) the RAW Zone file (at the bottom) reads _amazonses.domain.co. 1800 IN TXT “LOng+Key”

and the entry reads _amazonses “LOng+Key”

HTH

You have 3 CNAMEs containing “_domainkey” and 2 TXT records containing “amazonses”. Edit <strong>all</strong> of them and add a dot at the end of each so that e.g.: <br> <br><code>_amazonses.domain.co</code> becomes <code>_amazonses.domain.co.</code>

You have 3 CNAMEs containing “_domainkey” and 2 TXT records containing “amazonses”. Edit <strong>all</strong> of them and add a dot at the end of each so that e.g.: <br> <br><code>_amazonses.domain.co</code> becomes <code>_amazonses.domain.co.</code>

You have 3 CNAMEs containing “_domainkey” and 2 TXT records containing “amazonses”. Edit <strong>all</strong> of them and add a dot at the end of each so that e.g.: <br> <br><code>_amazonses.domain.co</code> becomes <code>_amazonses.domain.co.</code>

You can test your DigitalOcean DNS settings from the linux command line by doing this:

For TXT entries: host -t txt _amazonses.domain.ext ns1.digitalocean.com

For CNAME entries: host -t cname secrethash._domainkey.domain.ext ns1.digitalocean.com

Hope this helps some people.

@bringgers: It depends. It might take from 2 minutes to 3 days, you can read more on DNS propagation here: <a href=“http://serverfault.com/questions/82251/why-is-it-called-dns-propagation”>http://serverfault.com/questions/82251/why-is-it-called-dns-propagation</a>.

How many time to verified DKIM ? website is verified but DKIM Verification Status:pending verification is really 72hours ? <br> <br>This post is very helpful, thanks!

Hey I got the same issue as @taewoo Were you able to some that issue?

@taewoo: Can you post a screenshot of the records in DigitalOcean’s DNS Manager?

Hey guys… i had mine verified by Amazon is telling that some of the stuff is failing. <br> <br>here’s the screenshot <br> <br>http://s22.postimg.org/v8yomnxz5/ses_dkim.jpg <br> <br>Any thoughts on this?