Why NS in route53 are different to what is shown in whois.com?
I bought a domain directly in route53 and now want to route traffic to an EB environment but IT DOES NOT WORK. I am checking the Name Servers and they're not equal to what is shown in whois.com. I don't really know if that's normal because it might work with a different configuration inside route53 which I have no access or somehow that changed on its own.
- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi this is Abhi from AWS.
The whois nameservers should match the Route 53 name servers, as a pre-requisite to be able to resolve records in THAT Route 53 hosted zone. Depending on who you are working with to register the domain name, the process to update name servers will be different. Although, Route 53 provides both domain registration and domain hosting services, it is optional for customers to use both together. If you indeed are using both, you can follow this link to update the nameservers: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
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 4 mois
The records could be cached due to the TTL and the whois could be cached as well to avoid spam and similar issues