A question for those who know more about registry rules than me...
In the .example zone there can be five kinds of delegation NS record
(taking each record separately rather than the whole delegation NS RRset).
The requirements I am stating below are from the DNS point of view rather
than from the
On 23 Jun 2015, at 13:03, Tony Finch wrote:
A question for those who know more about registry rules than me...
In the .example zone there can be five kinds of delegation NS record
(taking each record separately rather than the whole delegation NS
RRset).
I think there are probably as many
* Tony Finch:
> A question for those who know more about registry rules than me...
Practically speaking, a registry-style zone operator must filter out
sibling glue, or there will be domain hijacks. The zone operator does
not know the structure of the reselling chain and cannot determine if
two
In message <87oak69rgm@mid.deneb.enyo.de>, Florian Weimer writes:
> * Tony Finch:
>
> > A question for those who know more about registry rules than me...
>
> Practically speaking, a registry-style zone operator must filter out
> sibling glue, or there will be domain hijacks. The zone opera
does this mean, for example, i have two nameservers,
ns1.example.pw.
ns2.example.pw.
for zone example.pw.
Now I want these two nameservers to be example.com, example.net,
example.org 's auth-nameservers. To do that we have to put these two
hostnames into com, net, org's zone space. And this c
