Geek Answers Handbook

The remote Route53 hosting zone is then recreated. Does not work?

I can’t figure it out and have drawn all the Amazon documentation that was looking for something and still cannot get it. I hope someone has dealt with this sooner.

So, I tried to get the Route53 domain to forward to the S3 bucket. By default, the "Hosted Zone" that Route53 makes after registering a domain does not seem to have received the alias of my S3 bucket, and Amazon's instructions talk about creating a new Hosted zone. Thus, I deleted the default Hosted Zone and made a new one, which then was able to get an alias in my S3 list, and I configured it to be transferred to my S3 bucket.

But now the domain just does not work at all. Anyway. It has entries like "NS" and "SOA", which are created by default, they are similar to my other domains that work. But that will not work. Even making CNAME on google.com does not work. I waited 24 hours to check if DNS is required for the update. And no luck.

I did something really stupid when I deleted the old zone and created a new one? Do I need to manually configure more in the new hosted zone to solve the problem?

+4
source share
1 answer

You should use hosted zone name servers as a domain name server, and not vice versa.

That is, you must do the following:

  • . ( )
  • .
  • .
  • , .
  • , .

, , ( )

+5

More articles:


All Articles