- 最新
- 最多得票
- 最多評論
I found the solution. At last when everything seems to fail and no help was coming, I started from zero.
First of all I make sure that I deleted route53 hosted zones. Then I reset my domain to point to default nameserver provided by GoDaddy. After an hour all of my website went down as it was pointing to default server. But it did worked as it reset everything to default.
Now I updated the NS provided by my hosting service (Hostinger) to bring my actual website back. And it worked; brought all of my subdomain website back.
It took 3 days of my time and business, I did not have Amazon Support Plan as well so my case is still un-assigned (without support no-one cares about SLA). I was even struggling with Hostinger Support Team and they also kept saying our team is working hard on you ticket. I would like to thank @Riku_Kobayashi for the reply.
Hello.
Did you purchase the domain on AWS?
Unless you migrate your domain registrar from AWS to another service, I think the NS records will continue to use AWS's NS records even if you delete the hosted zone.
You can transfer your domain to another domain registrar by following the steps in the document below.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-transfer-from-route-53.html
If you purchased it from another domain registrar and delegated the domain to Route53, I think you would be able to use it by changing it to the NS record you were originally using.
I purchased it from GoDaddy, and I have updated the nameserver there also, but still not reflecting. Also the issue is with sub-domain - that's what making it tough. My sub domain were hosted via AWS, primary domain is working fine.
相關內容
- AWS 官方已更新 3 年前
After digging deep I found this -> EDE(22): No Reachable Authority (at delegation api.mydomain.com)
But I still don't know the solution.