How to set an MX record in Route53 for a GoDaddy domain

amazon-route53amazon-web-servicesdomain-name-systemgodaddymx-record

Can't seem to find an answer to this question on AWS' forum, not in the Route53 manual, nor on Stackoverflow/Serverfault in a way that makes sense…and GoDaddy's support sure as heck ain't got an answer:

How do I set an MX record in Route53 for a GoDaddy domain?

My apex record and all CNAME records on Route53 are working correctly, pointing to my app on EC2. But I would love to be able to login to http://login.secureserver.net to check my web-based e-mail for this domain.

In case it's pertinent, GoDaddy's "Email Info Center" for the domain returns…

Domain settings can be invalid if the system cannot verify your email address or if the MX records are incorrect. For additional information, see Managing DNS for your domain names.

Type         Host                          IP Address
Nameserver   ns-AAA.awsdns-47.com          XXX.XXX.XX3.X22
Nameserver   ns-BBB.awsdns-55.net          XXX.XXX.XX5.X86
Nameserver   ns-CCCC.awsdns-24.org         XXX.XXX.XX6.X97
Nameserver   ns-DDDD.awsdns-11.co.uk       XXX.XXX.XX8.92

GoDaddy e-mail server settings listed as…

Server                      Standard Ports             Your Open Ports    
Incoming server (POP3):
pop.secureserver.net        110, 995 (SSL)             110, 995 (SSL)
Outgoing server (SMTP):
smtpout.secureserver.net    80, 3535, 25, 465 (SSL)    80, 3535, 25, 465 (SSL)

In the AWS console for Route53, is it just a matter of creating a MX record set with…

Name  = mail.mydomain.com
Value = 10 pop.secureserver.net 
        20 smtpout.secureserver.net

…???

Best Answer

To make things nice and clear, as some of the GoDaddy help articles are dead wrong:

enter image description here

You just need to paste the two records from the server settings into your Route 53 control panel as a new record.

enter image description here

The possible deception here is the the GD email panel will tell you you're wrong, but not what is right so you can make it right. Further, their help article tells you do look for the proper MX record settings under the Domains manager, where you'll not find them.

Finally, AWS is a tad confusing since they'll only let you enter a single apex domain MX entry. You can't have two as GD wants and some other zone managers allow, hence the need to double them up.

Hope this helps others! :)

Related Topic