<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">The reason we designed DNS is that you cannot possibly store all domains in the world locally. How do you think your solution scales if you not only need to store all worldwide domains but also their entire history ?<div><br></div><div>I have written about this in the past,</div><div><br></div><div><a href="https://nohats.ca/wordpress/blog/2012/04/09/you-cant-p2p-the-dns-and-have-it-too/">https://nohats.ca/wordpress/blog/2012/04/09/you-cant-p2p-the-dns-and-have-it-too/</a></div><div><br></div><div>Paul<br><br><div id="AppleMailSignature" dir="ltr">Sent from mobile device</div><div dir="ltr"><br>On Dec 13, 2018, at 16:58, ѽ҉ᶬḳ℠ via Unbound-users <<a href="mailto:unbound-users@nlnetlabs.nl">unbound-users@nlnetlabs.nl</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Hi<br>
<br>
If that has been discussed previously than I was not able to trace
it but being interested in whether there are plans to resolve
blockchain domains with Unbound?<br>
<br>
Thus far my understanding is that it would require:<br>
<ol>
<li>a transaction ID with the respective blockchain, and then <br>
</li>
<li>the initial download of the entire current blockchain, and</li>
<li>subsequent incremental downloads of the bits being
added/deleted to/from the blockchain</li>
</ol>
<p>The blockchain would contain the DNS for the domains and also the
security bits for each domain and thus there is no root and no
DNNSEC.</p>
</div></blockquote></div></body></html>