2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
2
Yes it matched what was listed apart from the MX that is missing. What I decided to do was to remove the @ sign, I had put earlier in front of the domain name in the record name box, then save it and guess what? When I clicked on the activate button on my google workspace, it worked. Thanks.
respondido hace un año
1
Hi, a couple of questions
- Did you register your domain through AWS Route53 or via an external registrar?
- If the latter, can you run
dig ns yourdomain.com(replace the yourdomain.com with your domain name) or enter your domain name into https://dnschecker.org/ns-lookup.php, then check that you see thensrecords pointing to AWS nameservers? - if you run
dig mx yourdomain.comor use https://mxtoolbox.com/MXLookup.aspx and enter your domain, do you see theMXrecords you've configured?
If you're registered with an external registrar, you need to ensure that the DNS configuration at the registrar is pointing to the AWS nameservers.
respondido hace un año
Contenido relevante
OFICIAL DE AWSActualizada hace 2 años- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 8 meses
I registered through Route53, and when I checked my NS records using the URL in your response, the MX records I configured did not appear on listed records.
If you look at the nameservers configured for the domain through either dig or the dnschecker URL, do they match the nameservers listed for the hosted zone?
It does take a while for updates to propagate but that should be hours rather than days.
Yes it matched what was listed apart from the MX that is missing. What I decided to do was to remove the @ sign, I had put earlier in front of the domain name in the record name box, then save it and guess what? When I clicked on the activate button on my google workspace, it worked. Thanks.