SES doesn't verify domain identity

Question

I have verified domains in SES "verified identities" screen many times before. Obviously, it is very simple, when DNS is hosted in Route53 hosted zone, but I also got domains verified in GoDaddy and Register.com without any problems. However, this time it doesn't. I added 3 CNAME records in DNS file, as usual. Compared 10 times that copy-paste happened properly; but SES stays in "Verification Pending" state for a day or two, and then switched to Unverified.
The only difference with all other domains is that reigstrar is Aplus.net. We use it for several other services; so we can't move to Route53 hosted zone at this time.

I don't mind putting domain name here, but guidelines suggest not to. What should I look into, besides the obvious?

UPDATE: I just tried another domain (with DNS hosted at hostgator) and it got verified in less than 5 minutes!

Answer

OMG - I figured it out! In aplus you have to put CNAME without your domain name. So, if AWS SES tells you to put `abcxyz._domainkey.example.com` - you actually have to put `abcxyz._domainkey` instead. Incidentally, in GoDaddy you *also* need to put the value without domain - but GoDaddy is smart enough to tell you that.

SES doesn't verify domain identity

関連するコンテンツ