Route 53 MX Record missing for Google Workplace Email Activation

Question

Our nonprofit uses Google Workspace for our email through a grant. We are migrating our website to a Lightsail instacne and have pointed the domain eyespy.org to the custom DNS nameservers for AWS Lightsail. The issue is now our email isn't working. I added an MX record via Route 53 and have been checking the Gmail setup and it still keeps saying we are missing the record. Any ideas?

Enter image description here

![Enter image description here](/media/postImages/original/IMU1RQ6FD8Qn2uD0sv_JgnBA)

![Enter image description here](/media/postImages/original/IM40NXFh0DTaigKPKcd2mt5Q)

Marcin Gondek · Answer

Hi Eye Spy,

First of all your domain **do not** point to proper AWS NameServers, on your screen there different that are configured for domain.
Your domain report:

```
Name Server: ns-1531.awsdns-63.org
Name Server: ns-1994.awsdns-57.co.uk
Name Server: ns-205.awsdns-25.com
Name Server: ns-811.awsdns-37.net
```

As far I can see on your screenshot, you have different ones - this is crucial, please update them where your register domain (on namecheap side) to be exactly the same on domain register company and on AWS side in Route 53.
You cannot change in easy way on Route 53 side, so you should update them on namecheap side.

Second the entry to MX should be:

eyespy.org. MX 1 smtp.google.com.

Remember about dots after your domain and after smtp.google.com. there should not be any @ or other letters/signs there.

Thanks,

Eye Spy · Answer

Thanks for the help. The Namecheap servers were configured to the custom DNS for AWS but it seems it was an MX record issue. The dev. we hired said the following and resolved the issue "Google Mx record also need to be added inside Lighsail DNS config."

I appreciate the comments!

Route 53 MX Record missing for Google Workplace Email Activation

Relevant content