Re: Blockchain DNS

[ѽ҉ᶬḳ℠ via Unbound-users]

Thank you for the link and the fine reading it makes. You make the point - the resolver is not the judge of the trust but handles and interprets the information handed down the chain of trust. It depends on the user whether to trust the institutions that established the chain of trust in the first place. Thus if users place their trust in a blockchain then it perhaps should not make a difference for a resolver to deal with the data provided by such a blockchain. Scaling is certainly a differen aspect of it and perhaps depends also on the data design also considering that DNSSEC/DMARC/DKIM/TLSA/CAA records are not involved. But is it not that blockchain transaction ID (wallet) apps are facing the same challenge and have to download the entire blockchain first and keep it then current with the bits beig removed/added? Blockchain might not be the saviour for all mankind challenges, like it is sometimes being promoted, but it is for the moment at least something interesting to consider. On 14.12.2018 00:12, Paul Wouters wrote: 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 ? I have written about this in the past, https://nohats.ca/wordpress/blog/2012/04/09/you-cant-p2p-the-dns-and-have-it-too/ Paul Sent from mobile device On Dec 13, 2018, at 16:58, ѽ҉ᶬḳ℠ via Unbound-users <unbound-users@nlnetlabs.nl> wrote: Hi 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? Thus far my understanding is that it would require: a transaction ID with the respective blockchain, and then the initial download of the entire current blockchain, and subsequent incremental downloads of the bits being added/deleted to/from the blockchain 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.