- 新しい順
- 投票が多い順
- コメントが多い順
Hi there, i had the same issue and was able to resolve it by removing the @ in the hostname from the MX record in route53, then try re-activation from google. Hopefully that helps.
Thank you for your reply, I cannot find any "@" sign anywhere in my MX record.
After creating the mx record, click on edit
-
Make sure the record name is left blank, don't add an @ sign there.
-
In the value field, add both values you get from google together at once. 1 SMTP.GOOGLE.COM 15 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.MX-VERIFICATION.GOOGLE.COM
-
TTL = 86400
-
Routing Policy = Simple Routing Save.
-
Head over to google verification to re-try verification. Also you can verify if your mx record values have fully propagated correctly by testing it at https://mxtoolbox.com/
-
This still helped me today. Thank you.
This resolved my issue, thank you!
Using dig, I was not able to find your MX record(s). Can you run this command and share the results?
aws route53 list-resource-record-sets \
--hosted-zone-id \
$(aws route53 list-hosted-zones --query HostedZones[?Name==\`earthspta.com.\`].Id --output text) \
--query ResourceRecordSets[?Type==\`MX\`]
Can you run this command in CloudShell and share the results?
aws route53 list-resource-record-sets \
--hosted-zone-id \
$(aws route53 list-hosted-zones --query HostedZones[?Name==\`earthspta.com.\`].Id --output text) \
--query ResourceRecordSets[?Type==\`NS\`]
where do I have to run this command?
when I run a test record in hosted zone it gives NOERROR message.
for both MX and NS records, there is a NOERROR message but still in gmail it says missing records all five of the MX records. its not letting me post the MX commands here
dig aws route53 list-resource-record-sets \
--hosted-zone-id \ $(aws route53 list-hosted-zones --query HostedZones[?Name==\`earthspta.com.\`].Id --output text) \ --query ResourceRecordSets[?Type==\`MX\`]-bash: aws: command not found Invalid option: --hosted-zone-id Usage: dig [@global-server] [domain] [q-type] [q-class] {q-opt} {global-d-opt} host [@local-server] {local-d-opt} [ host [@local-server] {local-d-opt} [...]]
You run the command I provided in CloudShell.
関連するコンテンツ
AWS公式更新しました 1年前- AWS公式更新しました 2年前
Cloud you please post the domain you are working with?
earthspta.com
So far it looks as though MX records for that domain are not resolvable. Could you share the records that you have created in AWS? You can redact any information that may be sensitive.
its not letting me post here
Were you able to resolve this? I am having the exact same issue. Bumping this.