On 13.12.2018 05:47, Joe Abley wrote:

I don't see that Unbound needs any modifications to consult a different root zone on a different set of servers, though.
With different root zones in existence unbound can currently handle only one.
Yes. This constraint is however inherent in the meaning of "root" and
not simply a restriction of inbound.

Depends what the definition of root is. Suppose that today's perspective would be the root of ICANN/IANA but really it can be any root such as OPENNIC and thus the question for alt-root in unbound. Who knows maybe other roots spring up too.

But perhaps the consideration of alt-root in the traditional sense it already obsolete in case the blockchain domains gain traction. Just read that there is no root in the traditional sense but rather a decentralized domain registry in the blockchain itself. Apparently it is claimed that there would be no need for DNSSEC.
Will be interesting to see how that would should shape the development of resolvers.

As I said, if you want to construct a new namespace as the union of
one or more others, that new namespace needs a new root. Point your
unbound at it if you're into that.

Not sure I am capable to follow your train of thought here - how do you construct a new namespace as the union of
one or more others?

Reply via email to