Score:-1

Domain unavailable after switching NS records

in flag

I have a situation where I'm using route 53 to manage our domain. The plan was to migrate the public hosted zone which we were using.

There are now two public hosted zones with the same domain. The plan was to switch the NS records of the one domain to point to the name servers of the other domain.

The problem is that now the domain is unavailable. Running Dig only returns the SOA record under the Authority section.

When I run

dig NS +norec <domain> @<authoritative server>

I only get the SOA.

There is no A record being returned even though both hosted zones have valid A records pointing to the same resource. The ttls was decreased on the NS records for both zones, and time was given for both of them to expire.

Anyone have any ideas on how I can proceed here?

Patrick Mevzek avatar
cn flag
"Anyone have any ideas on how I can proceed here?" Start by giving the name involved if you want people to help you, otherwise look at online troubleshooting tool DNSViz, and also both your registrars and DNS providers should be able to help you, did you ask them for guidance?
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.