41

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.

Improve this question

10 Answers 10

Reset to default
64

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

Improve this answer
Sign up to request clarification or add additional context in comments.

3 Comments

I had this problem too. Also you need to create all your MX records in one record. Even though my mail site said "add new MX records" plural. You don't create multiple MX records, you put all this in the same textbox on separate lines: 10 mydomain.com 20 mydomain.com 50 mydomain.com
Also found that this solves the same problem when using other mails servers, in my case adding a Microsoft mail server record.
Just got this to work at the date of this comment. All in the same textbox for the mx record. Priority number followed by a space and hit enter until you enter all the records provided by Google Workspace.
27

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.

Improve this answer

5 Comments

Hi Chris thanks for the help. I figured it out at the same time. I can also confirm the old console doesn't have the problem. Thanks for the help!
No problem, glad its "solved" for you. I have submitted feedback via the console to Route 53 team so hopefully this will get fixed :)
I used the new console and just prefixed with the numerals: 1 5 5 10 10
@haxpanel are you still experiencing the issue above? I could no longer reproduce it, just wondered if you could provide any steps to reproduce it now :)
@ChrisWilliams I used the old console which worked. Did not spend too much time on trying the new one after seeng the error I went to SO. :)
8

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

enter image description here

Improve this answer

Comments

5

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

Improve this answer

Comments

4

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

Improve this answer

Comments

3

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.

Improve this answer

Comments

2

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.

Improve this answer

Comments

1

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

Improve this answer

Comments

1

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.

Improve this answer

Comments

1

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

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.