<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 13.12.2018 05:47, Joe Abley wrote:<br>
<blockquote type="cite"
cite="mid:CAJhMdTPSW2atOY-DTyNmpmhhnfrA0+mMDhSeAzt5VRg26L0D_Q@mail.gmail.com"><br>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I don't see that Unbound needs any modifications to consult a different root zone on a different set of servers, though.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
With different root zones in existence unbound can currently handle only one.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Yes. This constraint is however inherent in the meaning of "root" and
not simply a restriction of inbound.</pre>
</blockquote>
<br>
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.<br>
<br>
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.<br>
Will be interesting to see how that would should shape the
development of resolvers.<br>
<br>
<blockquote type="cite"
cite="mid:CAJhMdTPSW2atOY-DTyNmpmhhnfrA0+mMDhSeAzt5VRg26L0D_Q@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">
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?
</pre>
</blockquote>
</body>
</html>