How do I test the glue records for a nameserver that isn't live yet?
I am more than happy testing glue records for domains that are live.
This time however we have just started the roll out of a large number of new nameservers. While we have created the glue records via the registrar's I am struggling to find a way to test the glue records without actually assigning them to a domain. Is this possible?
For clarification using real data (as of the time of writing)...
One of our current nameservers is ns12.dogsbodyhosting.net. so running a dig -t a @g.gtld-servers.net. ns12.dogsbodyhosting.net. correctly tells us that g.gtld-servers.net. cannot give as an ANSWER but that the AUTHORITY we need to speak to is ns12.dogsbodyhosting.net. and the ADDITIONAL (Glue) information we need of A and AAAA records. All good :-)
The problem: We have just created ns12.dogsdns.net. (as well as around 40 other new nameservers) and want to test that the glue for ns12.dogsdns.net. exists on the g.gtld-servers.net. and the other .net servers. However running dig -t a @g.gtld-servers.net. ns12.dogsdns.net. only shows us the glue records for the old DNS curently mapped to this domain and not the glue for ns12.dogsdns.net. that we are after.
To restate; We have created the glue records via the registrar but have no way of knowing if the registrar has done anything or if we made a typo entering all the records. So, how to we test these glue records without putting a domain live and hoping?
Even if we set up a burner domain using the new nameservers we would couldn't add all 60 nameservers to one domain.
Thank you in advance for any responses.
No comments:
Post a Comment