AWS announces AWS Interconnect – multicloud (preview), providing simple, resilient, high-speed private connections to other cloud service providers. AWS Interconnect - multicloud is easy to configure and provides high-speed, resilient connectivity with dedicated bandwidth, enabling customers to interconnect AWS networking services such as AWS Transit Gateway, AWS Cloud WAN, and Amazon VPC to other cloud service providers with ease.
AWS SES Custom From Domain DNS resolution issue
AWS SES is having trouble verifying that my MX and TXT records for my custom from domain are installed. It has already failed once, and I started it again.
The records are configured correctly in my Cloudflare dashboard. 
And doing a local lookup shows that the DNS records are actually there.
Is there anything I can do to convince SES that I in fact do have the required dns records installed?
- Newest
- Most votes
- Most comments
You have 2 MX records instead of one.
10 feedback-smtp.us-east-2.amazonses.com
20 feedback-smtp.us-east-2.amazonses.com
That could be the issue. Delete the 20 entry.
The rest looks good. Here is my SES config for comparison.
Based on the information provided, it appears that you're experiencing a domain verification issue with Amazon SES (Simple Email Service) for your custom "From" domain. While you've correctly configured the MX and TXT records in your Cloudflare DNS settings and can see them in local DNS lookups, SES is still having trouble verifying these records.
To address this issue and convince SES that you have the required DNS records installed, you can try the following steps:
-
Double-check the exact values of the TXT and MX records provided by Amazon SES. Ensure they match precisely with what you've entered in Cloudflare, including any underscores or periods.
-
If you haven't already, try adding the records without the proxy (orange cloud) enabled in Cloudflare. Sometimes, Cloudflare's proxy can interfere with DNS verification processes.
-
Wait for DNS propagation. Although your local lookup shows the records, it may take some time (up to 48 hours in some cases) for the changes to propagate fully across all DNS servers.
-
If you're using Route 53 for your DNS, you can try adding the TXT records there, as Amazon SES integrates more seamlessly with Route 53.
-
Verify that there are no conflicting DNS records for the same domain or subdomain.
-
If the issue persists, you can try initiating the domain verification process again through the Amazon SES console or API.
-
As a last resort, if none of the above steps work, you may want to contact AWS Support for further assistance. They can help investigate if there are any specific issues with the SES verification process for your domain.
Remember, patience is key in DNS-related issues. Sometimes, simply waiting a bit longer for full propagation can resolve the problem. If the verification continues to fail after these steps and a reasonable waiting period, reaching out to AWS Support would be the best course of action.
Sources
Verifying your domain for Amazon SES email receiving - Amazon Simple Email Service
Amazon SES domain verification TXT records - Amazon Simple Email Service
Verifying a domain with Amazon SES - Amazon Simple Email Service
Verifying your domain for Amazon SES email receiving - Amazon Simple Email Service
Relevant content
- asked 4 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
Thank you, this worked. This is very surprising, because the aws console itself told me to add both of those MX records.