Route53 not finding nameserver publically

there are now 3 such posts in this forum as per today, all with the same problem and same symptoms (me being one of them). The problem seems to be internally from AWS and not necessarily related to us.

Lets hope AWS finally looks at the forum posts of their paying customers and fixes this mess....

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 can't 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 reubenpuketapu.com, the name servers in the NS record match the name servers in the domain registration, but those two sets of name servers don't match the "master" name servers. This typically means that someone did the following:
~ Deleted the hosted zone that Route 53 created during domain registration
~ Created a new hosted zone
~ Updated the NS record to match the name servers in the domain rather than updating the domain to match the name servers in the new hosted zone

Here's how to fix that:

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 NS record to use the four name servers that you got in step 1. See "Editing Records":
   https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-editing.html

3. 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

Scott

Awesome!! Thanks Scott that worked perfectly!!

I wasn't aware that there were the THREE places, just the two :)

Legend

How does this related to instances hosted on Lightsail?
The Nameservers in my Lightsail Hosted Zone and my Route 53 Hosted Zone are different, meaning I have to adjust one set of nameservers.

Why do I have to setup Hosted Zones in both R53 and Lightsail anyway?

EDIT:
There is something funny going on here. According to documentation linked above, the R53 Nameservers shown via the radio button are considered MASTER NAMESERVERS, and all settings should follow these NS.
Now, I have a working hosted zone on AWS Lightsail which was given one set of NS as part of the AWS Lightsail configuration, which I then copied over to R53 and replaced the Edit Host Zone > NS settings there. This means that the MASTER NS and the Setting NS do NOT mach, yet the routing works perfectly as it should. Basically, I am treating the Lightsail NS as "Master NS" and adjust my other settings to follow those NS.

Now I am doing the same with a domain thats hosted on GoDaddy and forwarded to AWS Lightsail NS, which I then again updated in the R53 settings. Here it doesnt work and simply dont understand why. I dont understand why Lightsail and R53 are giving me two sets of Master NS in the first place, and given that both applications are part of the AWS Infrastructure, why is there a need to manually update the settings in the first place?

My domain has been unreachable for 4 days now and I am seriously asking myself why I am still sticking with AWS if this is all the support I can expect??

Hi,

I just found Lightsail documentation about how to use Route 53 to route internet traffic to a Lightsail instance, "Using Amazon Route 53 to point a domain to an Amazon Lightsail instance":

https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-using-route-53-to-point-a-domain-to-an-instance

Note that you're just creating a record in your Route 53 hosted zone, you aren't changing your name servers.

Follow the procedures above to confirm that your name servers are the same in all three places. After you change name servers for the domain registration, it can take up to two days for your domain to become available again on the internet because DNS resolvers cache name servers for that long. For an overview of how DNS works, including how resolver caching works, see "How Amazon Route 53 Routes Traffic for Your Domain" in the Route 53 Developer Guide:

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

Scott