CODEWITHSUNDEEP
amazon-web-servicesgmailamazon-route53google-workspacemail-server
stevec
stevec

Reputation: 52318

Configuring GSuite to work with route 53 - "MX record doesn't have 2 fields" error

I'm doing my best to follow GSuite's out of date instructions for routing emails to Gmail via a AWS Route 53 hosted zone (i.e. domain). Here are the outdated instructions:

enter image description here

I set the Values as instructed:

enter image description here

And I see:

Error occurred
Bad request.
(InvalidChangeBatch 400: MXRRDATANotTwoFields (MX record doesn't have 2 fields) encountered with '')

enter image description here

So it will not allow me to create the records.

Upvotes: 38

Views: 37597

Answers (10)

lemdon
lemdon

Reputation: 171

The official docs say to put a 1 in front of the smtp address, so: 1 smtp.google.com

Set TTL to 1hr (3600 seconds)

enter image description here

https://apps.google.com/supportwidget/articlehome?hl=en&article_url=https%3A%2F%2Fsupport.google.com%2Fa%2Fanswer%2F174125%3Fhl%3Den&assistant_event=welcome&assistant_id=gsuitemxrecords-gixvmm&product_context=174125&product_name=UnuFlow&trigger_context=a

Upvotes: 2

Jan Peeter
Jan Peeter

Reputation: 357

In the quick record create screen you need to enter it as follows: 10 yourmailserver.com

Upvotes: 1

Michal S
Michal S

Reputation: 1564

I know it does not sound like following the logic in Google workspace docs, but in April 2024 you need to remove @ from MX record domain.

Upvotes: 1

atazmin
atazmin

Reputation: 5687

This seem to worked for me in Route 53

enter image description here

enter image description here

https://support.google.com/domains/answer/3251241?hl=en&ref_topic=6293345#zippy=%2Cset-up-email-forwarding-with-custom-name-servers

Upvotes: 1

Matthew Brown
Matthew Brown

Reputation: 972

It appears that the cause of the problem is the nature or length of the whitespace between the priority and the host on each line. Reducing all this whitespace - on each line - down to a single space resolved the matter for me.

Upvotes: 2

Muhammad Hasan
Muhammad Hasan

Reputation: 168

So actually what MX record consists of is a priority and a host. The smaller the number the higher the priority. You can look it up on google as well.

Upvotes: 3

Coyo
Coyo

Reputation: 766

I had this problem with the new AWS console, but it turns out the problem was me. I had not read the instructions carefully enough.

There needed to be a numeric value (not explained) before the domain name or ip address in the value input. When I added the number, this worked for me in the new console.

enter image description here

Upvotes: 62

Kaizoku Gambare
Kaizoku Gambare

Reputation: 3413

You need to enter more than one value. This is working fine

enter image description here

Upvotes: 8

Chris Williams
Chris Williams

Reputation: 35188

I was able to reproduce this exact scenario when I used the new AWS Route 53 interface.

To resolve it I selected the use the old console. link from the top.

enter image description here

I then pasted the values below and it worked.

1 aspmx.l.google.com.
5 alt1.aspmx.l.google.com.
5 alt2.aspmx.l.google.com.
10 alt3.aspmx.l.google.com.
10 alt4.aspmx.l.google.com.

For now use the old console for doing this would be my suggestion.

Upvotes: 26

stevec
stevec

Reputation: 52318

There's something wrong with the new Route 53 console. I tried the exact same things in the old console and it worked immediately.

I hope AWS fix this soon. For anyone experiencing this issue in the mean time, try simply reverting to the old console by clicking the link on the left hand panel:

enter image description here

Upvotes: 5

Related Questions