Decentralized DNS with the Handshake Naming System
privateinternetaccess.com
Decentralized DNS with the Handshake Naming System
1–10 of 75 posts
Re: Decentralized DNS with the Handshake Naming System
#2Sounds like BitTorrent DHT, but for DNS. Is that the right take?
Re: Decentralized DNS with the Handshake Naming System
#3Kind of unrelated, but if there was ever a viable use case for blockchain beyond anarchist payment systems, it seems like it would be DNS.
Re: Decentralized DNS with the Handshake Naming System
#4Namecoin seemed like an interesting idea for decentralized registration, has it gone anywhere in the years I haven't been following it?
Re: Decentralized DNS with the Handshake Naming System
#5Yeah, because I want to have to mine a token every time I update my DNS settings. -_-
I get the "global, transparent, append only log" appeal, but for the reality of most people, I don't want to rely on a blockchain converging, or processing my update in a certain amount of time.
And that doesn't even cover companies (I don't agree with this, but it is a reality), that consider DNS entries private, and don't want to expose an easily scannable list of DNS entries .
Re: Decentralized DNS with the Handshake Naming System
#6DNS has always been decentralized. I mean, first sentence on wikipedia:
> The Domain Name System (DNS) is a hierarchical and decentralized naming system for computers, services, or other resources connected to the Internet or a private network.
Re: Decentralized DNS with the Handshake Naming System
#7Kind of unrelated, but if there was ever a viable use case for blockchain beyond anarchist payment systems, it seems like it would be DNS.
The closest thing there is right now would be ENS - the E stands for Ethereum.
ENS domain names can mainly be used for payment for now, so I'd be sending crypto to [domain].eth where the advantage is having a readable address instead of a random-looking string.
You can also host web pages on it (which I believe is helped by their IPFS) but that has seen limited use as of yet.
Re: Decentralized DNS with the Handshake Naming System
#8DNS has always been decentralized. I mean, first sentence on wikipedia: > The Domain Name System (DNS) is a hierarchical and decentralized naming system for computers, services, or other resources connected to the Internet or a private network.
From the article:
> While DNS is already fairly decentralized, the centralization exists because of ICANN’s gatekeeper control .... ICANN ultimately has control over what internet names are acceptable – and serves as a singular point of failure.
Re: Decentralized DNS with the Handshake Naming System
#9The article and Namebase faq go into some details, but just so I understand, what are the practical effects of this beyond decentralization?
- If I buy a TLD, will I own it in perpetuity, even after I die?
- If we're encouraging people to register their own TLDs, won't we run into the same limited-name/squatter problems as normal domains? I get that names are being released at a trickle, but that seems like it would just put off the problem a bit.
- Is this going to have the same environmental problems as Bitcoin, or will having fewer transactions mean that's less of an issue?
- Is Brave the only browser looking into this, or are we also seeing buy-in from browsers like Firefox and Chrome?
I'll read through whitepaper and learn the details, but if possible I'd like to know if it's worth my time to do so.
I'm not necessarily feeling great about the idea of having separate TLDs for every site, but I'll admit there is something attractive about being able to register 1 TLD as a namespace, one time, and then using subdomains for every other site I ever make. It's just not clear to me how that system would scale.
Re: Decentralized DNS with the Handshake Naming System
#10Yeah, because I want to have to mine a token every time I update my DNS settings. -_- I get the "global, transparent, append only log" appeal, but for the reality of most people, I don't want to rely on a blockchain converging, or processing my update in a certain amount of time. And that doesn't even cover companies (I don't agree with this, but it is a reality), that consider DNS entries private, and don't want to…
You don’t need to store the zone on chain - you can actually simply include NS records and have your authoritative server elsewhere - just like DNS today!