- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi,
The nameservers associated with the registrar should be the same as present in the hosted zone, so that correct nameservers are used for resolution.
The correct hosted zone is present with the nameservers:
ns-348.awsdns-43.com.
ns-955.awsdns-55.net.
ns-1200.awsdns-22.org.
ns-1950.awsdns-51.co.uk
as a dig to devonacloud.com using these nameservers gives and IP as seen below:
dig devonacloud.com @ns-348.awsdns-43.com +short
52.216.200.122
These nameservers should be the ones that are present with the registrar. Hence, When you click on your domain in Route 53, the name servers should be :
ns-348.awsdns-43.com.
ns-955.awsdns-55.net.
ns-1200.awsdns-22.org.
ns-1950.awsdns-51.co.uk
Please use the steps mentioned in the following document to add the above-mentioned nameservers associated with the hosted zone to your domain and remove the existing nameservers:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing
Hope this helps. Please write back in case you still face the issue post these steps.
Hi! I'm having the same exact issue with my domain. jennariddle.com.
Thanks in advance!
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- Réponse acceptéedemandé il y a 7 mois
- demandé il y a 6 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans