When the DNS blockchain forks, your browser just opens two new tabs instead of one and you get to visit both sites. Simple!
DNS-on-Blockchain is the next step after DNS-over-HTTPS
21–30 of 69 posts
Re: DNS-on-Blockchain is the next step after DNS-over-HTTPS
#22Yes, DNS should be like the old phone book — published regularly, pick one up anywhere & everywhere, look things up anonymously (granted, authenticity guarantees were somewhat lacking). My question - Sure blockchain can do this, but couldn’t a simpler DHT-based p2p system would work just as well or better? I like the distributed/anonymity/authenticity, but why is blockchain required?
Ipfs.io can solve this easily.
Ipfs requires a DNS server to bootstrap the P2P network, not a good idea.
Plus, Ipfs isn't that good when it comes to authentic data, if it's signed, there is only one key, so it's centralized again.
Re: DNS-on-Blockchain is the next step after DNS-over-HTTPS
#23So every DNS change is stored into the blockchain, forever? Will you have to download terabytes and terabytes of the blockchain in order to serve as a node? Why is that kind of audit history necessary? Why is the solution to every problem "blockchain" these days?
> Why is the solution to every problem "blockchain" these days? That is a trope and is no longer true. If you say blockchain is the solution you get laughed at.
Being laughed at doesn't seem to stop people from trying to solve problems by throwing more blockchain at it.
Re: DNS-on-Blockchain is the next step after DNS-over-HTTPS
#24Yes, DNS should be like the old phone book — published regularly, pick one up anywhere & everywhere, look things up anonymously (granted, authenticity guarantees were somewhat lacking). My question - Sure blockchain can do this, but couldn’t a simpler DHT-based p2p system would work just as well or better? I like the distributed/anonymity/authenticity, but why is blockchain required?
Ipfs.io can solve this easily.
What's the economic incentive structure to continue serving all the data in a performant manner?
Re: DNS-on-Blockchain is the next step after DNS-over-HTTPS
#25DoB will have to deal with some problems, especially bad actors; people will squat on domains, register typos (fscebook.com) or even bitflips (fabebook.com, b is one bitflip from c). Malware owners will run their C&C servers on domains.
Malicious domains will require someone removing them or blocking them even, unless you want the DoB namespace to turn into a cesspool of malware, phishing and nazis. Not something the average person wants.
Re: DNS-on-Blockchain is the next step after DNS-over-HTTPS
#26What is the proof? That the domain owner signed it with a certain key?
Is that key shared out-of-band? If so why do we even need the blockchain?
Re: DNS-on-Blockchain is the next step after DNS-over-HTTPS
#27Earlier quoted context omitted.
Ipfs.io can solve this easily.
Ipfs requires a DNS server to bootstrap the P2P network, not a good idea. Plus, Ipfs isn't that good when it comes to authentic data, if it's signed, there is only one key, so it's centralized again.
The implementation could easily change to not require DNS. You only need to find a single live node to bootstrap, so hardcoding a bunch of high-quality nodes works perfectly fine.
Also you don't need the "Where is IPFS?" DNS query to be anonymous in the first place.
Re: DNS-on-Blockchain is the next step after DNS-over-HTTPS
#28Actually, no.
Re: DNS-on-Blockchain is the next step after DNS-over-HTTPS
#29Earlier quoted context omitted.
Ipfs requires a DNS server to bootstrap the P2P network, not a good idea. Plus, Ipfs isn't that good when it comes to authentic data, if it's signed, there is only one key, so it's centralized again.
The implementation could easily change to not require DNS. You only need to find a single live node to bootstrap, so hardcoding a bunch of high-quality nodes works perfectly fine. Also you don't need the "Where is IPFS?" DNS query to be anonymous in the first place.
Then you still need to trust the initial node to not provide you with a poisoned peer list (ie, a list of peers that are wholely isolated from the proper IPFS network and provide bogus DNS answers).
And you need to bootstrap without DNS if you plan to actually replace DNS, not live beside it.
Re: DNS-on-Blockchain is the next step after DNS-over-HTTPS
#30Earlier quoted context omitted.
The implementation could easily change to not require DNS. You only need to find a single live node to bootstrap, so hardcoding a bunch of high-quality nodes works perfectly fine. Also you don't need the "Where is IPFS?" DNS query to be anonymous in the first place.
Then you still need to trust the initial node to not provide you with a poisoned peer list (ie, a list of peers that are wholely isolated from the proper IPFS network and provide bogus DNS answers). And you need to bootstrap without DNS if you plan to actually replace DNS, not live beside it.
Anything in the world could theoretically be poisoned. There's no point in worrying about attacks above a certain level of difficulty. If you can check in with a certain number of builtin peers, that's about as solid as we can make things.
> And you need to bootstrap without DNS if you plan to actually replace DNS, not live beside it.
Whatever. DNS itself is never going to shut down, so 100% replacement even for bootstrapping isn't a real concern. And if starting with 13 fixed IP addresses is good enough for DNS, then it should be good enough for IPFS.