Problem in nameserver: "missing nameservers reported by parent"

1

I am using Amazon AWS with the Route53 tool to manage records in my DNS zone. I've been able to set up the list of nameservers and their response on ping requests, but when doing a test on the IntoDNS > I run into this error, which is perhaps why the nameservers can not resolve the names.

Has anyone ever had a similar problem and managed to solve it in some way? I've researched a lot, but without success.

    
asked by anonymous 20.09.2017 / 20:39

1 answer

0

As this question did not receive any answers, I reported that I was able to solve the problem myself. I share my solution here for other people who go through the same situation.

  

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

It turns out that on AW5's Route53 (Amazon) management of the nameservers is a bit different. You can not use AWS nameservers on your domain dashboard (Registro.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 setting up all DNS records, you need to change.

In practice, what I'm talking about

Route53willprovideyouwithsomeuniquenameserversaftercreatingahostedzoneforyourdomain.Itturnsoutthattheydonothaveauthorityovertheirdomain,theyjustforward.ToresolvethisissueyouMUSTsetupyourownnameserversasfollows.

AccessRoute53,clickonthehostedareaofyourdomainandleavethesamerecordsasbelow:

  
  • EdityourNSrecordandregisterthenameserversyouwanttouse.Example:ns1.mydomain.com/ns2.mydomain.com/ns3/ns4...etc.

  •   
  • EdityourSOArecordandreplacethebeginningofthelinewithns1youjustcreated(seeimage,line3)

      
  • Createarecordforeachcreatednameserver(inthiscasewehave4nameservers[ns1,ns2,ns3andns4],thentherewillbe4recordsoftypeA.Innameput:ns1andinVALUEaddtheipthatittakes

  •   
  • Getipfromthenameserver

    SendpingrequeststoWindows,LinuxorMacusingtheterminal.Youwillusethe image 1 nameservers.

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

    • RepeatthisprocesswitheachofthenameserversprovidedbyAWSRoute53.
    • Notetheipsandresponsetime(time)providedinthepingprocess.
    • Nowwewillorderthenameserverwiththeshortestresponsetime(soweknowwhichoneisbesttouseasmain,thensecondary,third,etc.)

    Here'sthesecret

    Whenallthisconfigurationiscorrect,gotoyourdomainpanel(Whois,Registro.br,GoDaddy),clicktoinformthenameservers(eachpanelhasadifferentform,Icannotdetaileachone).Inmycaseit'stheWhoispanel.Justinformthenameserversthatwejustcreated(ns1.mydomain.com,ns2,ns3,ns4),saveandyou'redone!Problemsolved.

    *Changesmaytakeupto48hourstopropagate,sopleasewait.

    Nameservers

    Toensure,IusedtheWhoispanelandaddedtheChildNameservers,eachpointingtotheirrespectiveIP.Thismaybeasomewhatunnecessarystep,butIthoughtitbesttomakesure.

    * The reported ips were obtained in the ping step.

        
    25.09.2017 / 21:33