DNS MX settings not propagating

0

I entered MX records for my Google Workspaces emails yesterday and they still haven't propagated. AWS touts 60 second propagation worldwide, right? Is there anything I can do to push this through?

My domain is swartztrailer.com and it is registered at Godaddy pointing to AWS nameservers. I set up a Route 53 hosted zone.

Edited by: Swartz on Mar 24, 2021 11:57 AM

Edited by: Swartz on Mar 24, 2021 11:58 AM

Swartz
已提問 3 年前檢視次數 623 次
3 個答案
0

Hello,

The MX records are not created in the Route 53 hosted zone associated with domain, as we can see in dig output no answer is returned.

$ dig swartztrailer.com MX
; <<>> DiG 9.11.18 <<>> swartztrailer.com MX
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40101
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;swartztrailer.com. IN MX
;; AUTHORITY SECTION:
swartztrailer.com. 300 IN SOA ns-1410.awsdns-48.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

Make sure you create the MX record in the hosted zone associated with the AWS NS (below) you specified in the domain registration.

$ dig swartztrailer.com NS +short
ns-1410.awsdns-48.org.
ns-1680.awsdns-18.co.uk.
ns-412.awsdns-51.com.
ns-953.awsdns-55.net.

You can refer to instructions mentioned in this post - https://forums.aws.amazon.com/thread.jspa?messageID=978618

AWS
支援工程師
Peter_N
已回答 3 年前
0

As far as I know, I did. I created the record as follows in Route 53:

Domain name: swartztrailer.com
Type: Public Created by: Route 53
Record count: 4
Description: -
Hosted zone ID: Z07035111EILH7AXWJ70F

When I click into the domain link above it shows the record I entered:

Record name: swartztrailer.com
Type: MX
Routing policy: Simple Differentiator -
Value/Route traffic to: 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.
15 ******************************.mx-verification.google.com.

I'm using godaddy, and I don't see any place to add an MX record. It tells me the domain is managed by AWS.

I think it might be due to the fact that Route 53 has it's own nameservers for the created hosted zone. The ones I entered were before I started using Route 53. I'm going to change them now and see if that works. See step 7:1 here: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html

EDIT: Yep. That was the problem.

Edited by: Swartz on Mar 25, 2021 6:46 AM

Swartz
已回答 3 年前
0

I needed to change my Nameservers to the ones listed in the Route 53 hosted zone (click arrow to expand top bar).

Swartz
已回答 3 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南