News for hackers. Stuff that matters.

A comment on Decentralized Naming and Certificate Authority. Parent comment

Re:Decentralized Naming and Certificate Authority by tynes on Wednesday February 12, 2020 @02:38PM (#22312016)
In blockchains, there is a difference between consensus and policy. The way that the Handshake recursive resolver works is not based on consensus. This means that people can insert rules for delegating a particular request to ICANN or to the Handshake authoritative resolver. It currently checks the Handshake authoritative resolver first, then falls back to ICANN.

If this behavior is easily configurable/shared and open source, then people can opt into whatever configuration that best suites their needs.

[ Parent | on HN ]
Re:Decentralized Naming and Certificate Authority by Ajedi32 on Wednesday February 12, 2020 @02:44PM (#22312077)
Awesome, that's good to hear! Sounds like a pretty easy fix then. Users just need to configure the recursive DNS resolver to delegate existing TLDs to ICANN and that fixes the compatibility issue. I might actually give that a try at some point.
[ Parent | on HN ]