On 09.12.2018 22:35, David Conrad wrote:
On Dec 9, 2018, at 4:23 PM, ѽ҉ᶬḳ℠ via Unbound-users <[email protected]> wrote:
On 09.12.2018 22:11, Anand Buddhdev wrote:
Your question doesn't even make sense. How would unbound know to resolve
TLD1 via root, and TLD2 via alt-root?
TLD for respective zones are stored in the respective root zone files and thus are distinguishable.
How do you distinguish “.” from “.”?

As initially mentioned with a syntax e.g. name: . and alt-name: .

How do you distinguish “.TLD” in the root from “.TLD” in the alt-root?

From the root zone file provided by the respective root and as initially mentioned with a syntax e.g. name: . and alt-name: .

Which root hints would you use?

The ones provided by the respective root and as initially mentioned with a syntax e.g. root-hint and alt-root-hint.

Which KSK would you use?

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.


Reply via email to