3 個答案
- 最新
- 最多得票
- 最多評論
1
Looks like your not using the correct name servers. Especially you have 8 listed for your domain where AWS only supplys 4
I would check the NS records in your Zone and update the Domain Glue records to point to the correct name servers.
0
Hi Chao,
Missing "." at the end of each value? So
1 smtp.google.com. <-- dot here
15 another-record.com. <-- dot here
Thanks,
已回答 5 個月前
0
I don't see any MX records in that zone:
% dig uniscrm.link -t MX
; <<>> DiG 9.10.6 <<>> uniscrm.link -t MX
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17659
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;uniscrm.link. IN MX
;; AUTHORITY SECTION:
uniscrm.link. 900 IN SOA ns-1052.awsdns-03.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
Check that you are putting them into the correct Route53 hosted-zone, you can have multiple Route53 Hosted Zones with the same domain name. The one that you need to create the records in has the following delegation set:
% dig uniscrm.link -t NS +short
ns-295.awsdns-36.com.
ns-1741.awsdns-25.co.uk.
ns-1052.awsdns-03.org.
ns-949.awsdns-54.net.
相關內容
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前