1 Answer
- Newest
- Most votes
- Most comments
0
Standard wait time for DNS changes typically propagate within 48 hours and SES automatically checks for DNS records periodically. Since you've already waited 24+ hours and can confirm the CNAME records are resolving correctly with dig +short, the issue is likely not propagation delay.
Verify the exact CNAME format:
# Check all your SES CNAME records
dig _amazonses.example.com CNAME +short
dig [selector]._domainkey.example.com CNAME +short
# Use AWS's DNS servers directly
dig @ns-1.awsdns.com _amazonses.example.com CNAME +short
OR Sometimes for few domain it requires entering CNAME records WITHOUT the domain suffix. For example:
Name field: Enter just _amazonses (not _amazonses.example.com) Value field: Enter the full AWS value as provided If the records are resolving correctly via dig but SES still shows pending, this is likely a SES-side verification issue rather than a DNS problem.
answered a year ago
Relevant content
asked 2 years ago
asked 5 months ago
- AWS OFFICIALUpdated 2 years ago
