- Newest
- Most votes
- Most comments
When you create an SES identity with Domain as an Identity type, you are asked to perform DKIM-based domain verification. To complete this verification, you are asked to copy the generated CNAME records to you domain's DNS provider.
If you create these records there, then verification process does not take much time. Instead, it is completed within few minutes.
The key thing here is to make sure that you have created proper CNAME records in your domain with proper values as shown in the picture below. When creating CNAME, don't include your domain name as that is included by default, just add the first segment till ._domainkey
.
In my experience, even a second domain has never been on hold for a long period of time.
Try redoing the domain verification as described in the following document, or check to see if the correct domain is registered.
https://repost.aws/knowledge-center/ses-domain-stuck-pending-verification
By the way, are the first and second domains in separate host zones?
If they are using the same host zone, it would be a good idea to check for differences in domain verification settings.
Relevant content
- Accepted Answerasked 6 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago