4 ms·

i wonder why they dont mention a blockchain solution to dns problems.

jgrahamc 8y ago
Sure, let's use blockchain for everything. I mean, why not? It's clearly the perfect solution to every problem that has ever occurred in any distributed system.
- return1 8y ago
  how is it not a better solution in this case?
  - jgrahamc 8y ago
    What DNS problem are you solving with blockchain and how?
    - return1 8y ago
      security, like DNSSEC does. but only 1% of domains use DNSSEC. there are other advantages, like uncensorability, direct access to dns records, disadvantage is speed I am not advocating "blockchain for every problem", but name resolution is a good fit - if only there were blockchains in the 80s. there are already implementations: https://medium.com/@jgm.orinoco/ethdns-an-ethereum-backend-for-the-domain-name-system-d52dabd904b3 https://medium.com/@jgm.orinoco/ethdns-an-ethereum-backend-f...
      - jgrahamc 8y ago
        So, why not work for further DNSSEC deployment instead of coming up with a new solution? I don't see how blockchain makes things better.
      - rlpb 8y ago
        > but only 1% of domains use DNSSEC. And what percentage of domains use "blockchain"?
      - cjbprime 8y ago
        This implementation requires you to download tens of gigabytes of data to any device that you want to resolve a name on. It's a non-starter. (For that matter, last time I looked, Ethereum was at a point where it's not actually possible to "keep up" with the blockchain on a machine that isn't in a datacenter.)
superkuh 8y ago
Or a solution like hash based domains that Tor uses. I know a lot of commercial sites balk but it really is more secure. And instead of just leasing a domain on the whims of a company easily swayed by politics and lawyers you actually own your domain on the Tor network.
- jgrahamc 8y ago
  You wonder why we don't propose replacing all of DNS with Tor .onion addresses? After all, it's so easy to remember/verify that DuckDuckGo is https://3g2upl4pq6kufc4m.onion/ https://3g2upl4pq6kufc4m.onion/
  - superkuh 8y ago
    It is easier than ever to brute force generate a readable Tor address. Even with my 2010 graphics card I generated superkuhbitj6tul.onion (for my superkuh.com and superkuh.bit (namecoin) domains) in about 30 minutes. With todays graphics cards you can go much further than that number of characters. But yeah, there's still the trailing sequence and companies that don't understand how simple that is.
    - jgrahamc 8y ago
      Even if you made this a one click service the trailing characters are going to be a killer. Companies care a lot about their brand. And it would require a total mindset change for people to verify that they are going to superkuhbitj6tul.onion and not superkuhbit6g4tfr4.onion by verifying the cert that was offered up by the destination site.
      - superkuh 8y ago
        >and not superkuhbit6g4tfr4.onion You mean superkuhbit6g4tf.onion. Although longer Tor based address hashes are coming soon for better security (https://blog.torproject.org/tors-fall-harvest-next-generation-onion-services https://blog.torproject.org/tors-fall-harvest-next-generatio...) so the trailing length of random chars will be even longer. Kind of mitigates my objection. Still, Tor hidden services come with DoS/DDoS protection built in as well. Something Cloudflare and it's centralized service doesn't like to acknowledge.

Sure, let's use blockchain for everything. I mean, why not? It's clearly the perfect solution to every problem that has ever occurred in any distributed system.

return1 8y ago
how is it not a better solution in this case?
- jgrahamc 8y ago
  What DNS problem are you solving with blockchain and how?
  - return1 8y ago
    security, like DNSSEC does. but only 1% of domains use DNSSEC. there are other advantages, like uncensorability, direct access to dns records, disadvantage is speed I am not advocating "blockchain for every problem", but name resolution is a good fit - if only there were blockchains in the 80s. there are already implementations: https://medium.com/@jgm.orinoco/ethdns-an-ethereum-backend-for-the-domain-name-system-d52dabd904b3 https://medium.com/@jgm.orinoco/ethdns-an-ethereum-backend-f...
    - jgrahamc 8y ago
      So, why not work for further DNSSEC deployment instead of coming up with a new solution? I don't see how blockchain makes things better.
    - rlpb 8y ago
      > but only 1% of domains use DNSSEC. And what percentage of domains use "blockchain"?
    - cjbprime 8y ago
      This implementation requires you to download tens of gigabytes of data to any device that you want to resolve a name on. It's a non-starter. (For that matter, last time I looked, Ethereum was at a point where it's not actually possible to "keep up" with the blockchain on a machine that isn't in a datacenter.)

superkuh 8y ago

Or a solution like hash based domains that Tor uses. I know a lot of commercial sites balk but it really is more secure. And instead of just leasing a domain on the whims of a company easily swayed by politics and lawyers you actually own your domain on the Tor network.

jgrahamc 8y ago
You wonder why we don't propose replacing all of DNS with Tor .onion addresses? After all, it's so easy to remember/verify that DuckDuckGo is https://3g2upl4pq6kufc4m.onion/ https://3g2upl4pq6kufc4m.onion/
- superkuh 8y ago
  It is easier than ever to brute force generate a readable Tor address. Even with my 2010 graphics card I generated superkuhbitj6tul.onion (for my superkuh.com and superkuh.bit (namecoin) domains) in about 30 minutes. With todays graphics cards you can go much further than that number of characters. But yeah, there's still the trailing sequence and companies that don't understand how simple that is.
  - jgrahamc 8y ago
    Even if you made this a one click service the trailing characters are going to be a killer. Companies care a lot about their brand. And it would require a total mindset change for people to verify that they are going to superkuhbitj6tul.onion and not superkuhbit6g4tfr4.onion by verifying the cert that was offered up by the destination site.
    - superkuh 8y ago
      >and not superkuhbit6g4tfr4.onion You mean superkuhbit6g4tf.onion. Although longer Tor based address hashes are coming soon for better security (https://blog.torproject.org/tors-fall-harvest-next-generation-onion-services https://blog.torproject.org/tors-fall-harvest-next-generatio...) so the trailing length of random chars will be even longer. Kind of mitigates my objection. Still, Tor hidden services come with DoS/DDoS protection built in as well. Something Cloudflare and it's centralized service doesn't like to acknowledge.