Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

SES and Cloudflare (multiple errors)

0

I am setting up SES for the first time. I am editing DNS records on Cloudflare. I am copying and pasting exactly from the "Get DNS Records" from the setup screen.

DKIM CNAMES worked fine. I started getting errors with the MAILFROM MX.

I receive the following errors: Change the content of your MX record to be a hostname (and not an IP address). For more details, refer to https://developers.cloudflare.com/dns/manage-dns-records/how-to/email-records/#add-mx-records.

The information that I am inputting is again copied exactly from the Amazon DNs setup screen. hostname is as follows: send.mydomain.com where 'mydomain' is my actual domain. the MX value is: 10 feedback-smtp.us-east-2.amazonses.com

Topics
Front-End Web & MobileBusiness Applications
Tags
Amazon Simple Email Service
Language
English

asked a year ago354 views

1 Answer
1
Accepted Answer

When setting up MX records for AWS SES in Cloudflare, you're encountering an error because of how the MX record format needs to be entered in Cloudflare's interface.

The issue is that the "10" in "10 feedback-smtp.us-east-2.amazonses.com" is not part of the hostname itself - it's actually the priority value for the MX record. In Cloudflare's DNS management interface, you need to separate these two pieces of information:

  1. In the "Priority" field: Enter "10"
  2. In the "Value" or "Target" field: Enter only "feedback-smtp.us-east-2.amazonses.com" (without the "10" prefix)

This is a common confusion when setting up MX records across different DNS providers. The AWS console shows the complete MX record format with the priority number included, but most DNS providers like Cloudflare have separate fields for the priority and the hostname.

Once you make this adjustment, the Cloudflare error should be resolved, and your SES MAIL FROM domain setup should proceed correctly.
Sources
Cloudflare DNS not accepting my AWS Workmail MX Value | AWS re:Post
SES get set up MX recorded is invalid. Is a bug? | AWS re:Post
AWS SES Custom From Domain DNS resolution issue | AWS re:Post

answered a year ago

EXPERT

reviewed a year ago

  • Thomasck
    a year ago

    Thank you. You are correct. This allowed me to save the record. Thank you again.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content