DNS_PROBE_FINISHED_NXDOMAIN error from ARecord to S3 static website

Hi,

Name servers appear in three places, and typically they should all be in synch:
~ The name servers that Route 53 assigns to a hosted zone when you create it. These are the "master" name servers and cannot be changed. Name servers in the other locations usually match these.
~ The name servers in the NS record in the hosted zone.
~ The name servers that are associated with the domain registration. These are the name servers that control which DNS configuration is in use.

For yoloyoloyolo.com, the "master" name servers match the name servers in the NS record, but the name servers in the domain registration are different.

To fix that, do the following:

1. Get the name servers that Route 53 assigned to the hosted zone when you created it. See "Getting the Name Servers for a Public Hosted Zone" in the Route 53 Developer Guide:

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/GetInfoAboutHostedZone.html

2. Update the domain registration to use the four name servers that you got in step 1. See "Adding or Changing Name Servers and Glue Records for a Domain":

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html

After you finish, it will take a couple of days for you to be able to see your website again because DNS resolvers typically cache the names of name servers for two days. (Folks who use different DNS resolvers will be able to see your website as soon as you make the change. You might also be able to see your website from your phone.) For an overview of how DNS works, including the part about resolver caching, see "How Amazon Route 53 routes traffic for your domain":

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-dns-service.html#welcome-dns-service-how-route-53-routes-traffic

For more information about using an S3 bucket for a static website, see "Getting Started":

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/getting-started.html

Scott