nameserver registration

[Jorg W.]

2011/6/19 Michael Sinatra <michael at rancid.berkeley.edu>:
> On 06/18/11 15:23, Chris Thompson wrote:
>>
>
>> Of course, at the root zone level, *all* NS records need either
>> "required glue" or "sibling glue", because every single one of them
>> is somewhere under the root zone. At least, until the aliens contact
>> us and we get the Internet spliced into the Galactinet ..


So, every nameserver's hostname with their IP addresses must exist in
root zone (the ".") ?


>>
>> Also, the "required glue" + "sibling glue" desideratum is not always
>> enough. Consider
>>
>> foo.com. NS ns1.bar.net.
>> foo.com. NS ns2.bar.net.
>>
>> and
>>
>> bar.net. NS ns1.foo.com.
>> bar.net. NS ns2.foo.com.
>>
>> Neither seems to to need glue in either "com" or "net", but without
>> either the domains cannot be resolved. This was a significant issue
>> when VeriSign changed the way the *.gltd-servers.net responded last
>> year.
>
> That's a good example (dare I say the canonical one?).  I was thinking of
> even simpler cases, such as where you are at least a layer below SLD.
>  Consider:
>
> baz.org.  NS ns1.dns.podunk.edu.
> baz.org.  NS ns2.dns.podunk.edu.
>
> and
>
> dns.podunk.edu. NS ns1.dns.podunk.edu.
> dns.podunk.edu. NS ns2.dns.podunk.edu.
>
> In theory, you "should" only need glue in podunk.edu, but podunk.edu isn't
> under the control of any registry (or registrar for that matter).  If the
> registrar for baz.org wants to be sure that things are going to work--and
> that they will stay working--then you need appropriate glue at a higher
> level.
>
> Because registrars (and even registries) can't always control the immediate
> parent of the NS, they require registration of the nameserver to allow for
> glue to be placed at higher levels.
>


The answer above is excellent, thanks.
And, is there a way to know how my nameservers are registered in any
level of zone?

Jorg.