<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 09.12.2018 22:35, David Conrad wrote:<br>
<blockquote type="cite"
cite="mid:7F2EBBEA-76FA-45C1-83EB-B437224C0EF2@virtualized.org">
<pre class="moz-quote-pre" wrap="">On Dec 9, 2018, at 4:23 PM, ѽ҉ᶬḳ℠ via Unbound-users <a class="moz-txt-link-rfc2396E" href="mailto:unbound-users@nlnetlabs.nl"><unbound-users@nlnetlabs.nl></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On 09.12.2018 22:11, Anand Buddhdev wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Your question doesn't even make sense. How would unbound know to resolve
TLD1 via root, and TLD2 via alt-root?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">TLD for respective zones are stored in the respective root zone files and thus are distinguishable.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
How do you distinguish “.” from “.”?</pre>
</blockquote>
<br>
As initially mentioned with a syntax e.g. name: . and alt-name: .<br>
<br>
<blockquote type="cite"
cite="mid:7F2EBBEA-76FA-45C1-83EB-B437224C0EF2@virtualized.org">
<pre class="moz-quote-pre" wrap="">
How do you distinguish “.TLD” in the root from “.TLD” in the alt-root?</pre>
</blockquote>
<br>
From the root zone file provided by the respective root and as
initially mentioned with a syntax e.g. name: . and alt-name: .<br>
<br>
<blockquote type="cite"
cite="mid:7F2EBBEA-76FA-45C1-83EB-B437224C0EF2@virtualized.org">
<pre class="moz-quote-pre" wrap="">
Which root hints would you use?</pre>
</blockquote>
<br>
The ones provided by the respective root and as initially mentioned
with a syntax e.g. root-hint and alt-root-hint.<br>
<br>
<blockquote type="cite"
cite="mid:7F2EBBEA-76FA-45C1-83EB-B437224C0EF2@virtualized.org">
<pre class="moz-quote-pre" wrap="">Which KSK would you use?</pre>
</blockquote>
<br>
Have not looked into DNSSEC ecosystem for blockchain domains or
OPENNIC domains. Yet I would assume that they would leverage their
own KSK for domains that ICANN does not handle.<br>
<blockquote type="cite"
cite="mid:7F2EBBEA-76FA-45C1-83EB-B437224C0EF2@virtualized.org">
</blockquote>
<br>
</body>
</html>