- 最新
- 投票最多
- 评论最多
Hi Steve,
Here are the Route 53 screenshots and also checks from https://whois.domaintools.com which seem to show different name servers for some reason.
I also flushed https://developers.google.com/speed/public-dns/cache and it made no difference to queries against 8.8.8.8
Any help appreciated.
thanks
Andrew
Hmm yes I can see that the name servers listed for the domains are different and match the ones reported by the other sites.
The question is, how can I fix it? I selected "create hosted zone" and that's the name servers it put in. I can change the name servers in the NS records but is that enough?
You can change the values in the Registered domains section of the Route 53 Console, instructions are here https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html
Or update the NS records in the Hosted zones of the Route 53 Console, see steps 4 thru 9 of https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html
Whichever option you pick, by the end of it everything needs to match up.
On the face of it, the whois output looks like they are both using Route 53 for their name service, which is what you would expect.
What's the zone apex record value when you view each of the Public Hosted Zones in Route 53? https://console.aws.amazon.com/route53/v2/hostedzones#
相关内容
AWS 官方已更新 7 个月前- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
Thanks for the screengrabsm easy to see that there's a mismatch - all NS records (4 out of 4) need to match for each domain.
When you look at each registered domain in turn in https://console.aws.amazon.com/route53/domains/home#/ what are the nameservers associated with these, and do they align with the NS records in the public hosted zones?