Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM™<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1790.msg27396#msg27396">Quote from: ribuck on December 06, 2010, 05:04:01 PM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1790.msg27382#msg27382">Quote from: kiba on December 06, 2010, 04:25:14 PM</a></div><div class="quote">I am making it my project to write a BitDNS client.</div><br/>Before we go too far down the track, can we agree on a project name? I'm uneasy about BitDNS, because we aren't writing a Domain Name Server. How about BitDomains, or DomainChain?<br/></div><br/>In a way, we are writing a Domain Name Server.&nbsp; The hope here is that eventually the data we throw into this database is going to be extracted and used with the current DNS architecture as used on the internet, where computers would have the DNS resolution pointing to this database as a "fall back" position if it can't be resolved through the regular DNS channels.&nbsp; That is how OpenDNS is currently working right now.<br/><br/>The only differences here is that we aren't relying upon a central server to act as a gatekeeper of this information, and it would be something that you could simply put into the search path through the network configurations of your own.<br/><br/>Getting the DNS protocol hooks working is to me a much more trivial thing than getting the domain registration itself going, however.&nbsp; Once you can demonstrate that the domain registration is working and that the domain name can be resolved cleanly, getting the DNS portion working is simply plugging through the RFC protocol documents to make sure you get that side working.&nbsp; The revolutionary thing isn't the DNS server software (which can already be downloaded for free as in beer and speech) but rather the decentralized database keeping track of this stuff and securing the data from getting tampered with.</div> text/html