- 最新
- 最多得票
- 最多評論
In the second case, you don't need to wait 2 days, it should be available a lot faster.
In the first question, I have no idea why it worked. If the NS are different, then your HostedZone can't manage your domain, because domain is pointing to different NameServers.
I'm writing new answer so it will send notification :)
Please check once again Route53 Hosted Zone and Domain if the NS records are the same.
It's very important that in Hosted Zone you need .(dot) after each of the NS records. Please verify it as well.
Sorry not to update here. My issue was resolved a day ago.
- In Hosted Zone , there are two sections : Details and Records. All the while I was trying to keep Records and Domain registrar in synch. After keeping these two ( Records and Domain registrar) same as "Hosted zone details" , the problem got resolved.
- To fasten up the updates, I made the TTL of NS record an hour. After WHOIS reflected my changes, I reverted back the TTL to two days.
- I remember seeing the '.' at the end of NS some where/some time. Now if I see ,the 3 places are not having '.' as suffix and still everything works fine.
Perfect! Good that you fix it :)
It is now more than 48 hours, my website is still down. There is no change in DIG responses. If I give it against one of my NS, I still get REFUSED error.
then I think you must do something wrong. Please check it once again if the NS records in Hosted Zone are the same as in the Domain in Route 53
This is a tough one to diagnose remotely but this page could provide some help? https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html
相關內容
AWS 官方已更新 2 年前- AWS 官方已更新 8 個月前
- AWS 官方已更新 3 年前
Thanks for the answer.
For Point2, should I just wait or is there anything I can do to make it fast?
Unfortunately, you need to wait, but last time when I was changing it, it was ready in a few hours.