Nameserver problem: "Missing nameservers reported by Parent"

Question

I am using Amazon AWS with Route53 tool to manage my DNS zone records. I was able to configure the nameservers listing and their response in ping requests, but when performing a Intodns I come across this mistake, which is perhaps the reason that the nameservers can’t solve the names.

Has anyone had similar problem and managed to solve somehow? I’ve researched a lot, but without success.

Answer 1

As this question received no answers, he informed that I was able to solve the problem alone. I share here my solution to other people who are going through the same situation.

Problem: "Missing nameservers reported by Parent" and "Missing nameservers reported by your nameservers".

It turns out that in AWS’s Route53 (Amazon) the management of nameservers is a little different. You may not use the AWS nameservers in your domain dashboard (Register.br, Whois, Godaddy, etc.). At the beginning of the settings you use them so that you can access the server and perform installations, etc. After configuring all DNS records it is necessary to change.

In practice, what I’m talking about

Route53 will provide you with some unique nameservers after you create a hosted zone for your domain. It turns out they don’t have authority over their domain, they just forward. To solve this problem you MUST set up your own nameservers as follows.

Go to Route53, click on the hosted zone of your domain and leave the same image records below:

1. Edit your NS-type record and register the nameservers you want to use. E.g.: ns1.meudominio.com.br / ns2.meudominio.com.br / ns3 / ns4... etc.

2. Edit your SOA record and replace the beginning of the line with ns1 that you just created (see in the image, line 3)

3. Create a record for each nameserver created (in case we have 4 nameservers [ns1, ns2, ns3 and ns4] , then it will be 4 records of type A. In name put: ns1 and in VALUE add the ip that leads to nameserver. See below for how to get ips for each nameserver.

Get ip from nameserver

Send ping requests on Windows, Linux or Mac using the terminal. You will use the nameservers from image 1.

Ex.: ping ns-1190.awsdns-20.org

• Repeat this process with each of the nameservers provided by AWS Route53.
• Note the ips and response time (time) provided in the ping process.
• Now let’s order the nameserver of the shortest response time (so we know which is best to use as the main, then secondary, third, etc.)

Here is the secret

When all this configuration is correct, go to your domain dashboard (Whois, Register.br, Godaddy), click to inform the nameservers (each dashboard has a different shape, I can’t detail each one). In my case, it’s the Whois panel. Simply inform the nameservers we just created (ns1.meudominio.com.br, ns2, ns3, ns4), save and you’re done! Problem solved.

*Changes can take up to 48 hours to propagate, so please wait.

Nameservers children

To be sure, I used the Whois panel and added the Child Nameservers, each pointing to their respective IP. This may be a step somewhat unnecessary, but I thought it best to ensure.

*The reported ips were obtained in the ping step.