bitname.org TLD
Posted: Sun May 15, 2011 4:14 pm
I've just enabled an experimental new type of "resolver" for namecoin domains:
One issue with the current .bit TLD is adoption, as only a small subset of users will install/configure a custom resolver. Instead, I think it would be better (or at least a good alternative) to resolve namecoin names as subdomains of different "traditional" domains (such as "bitname.org"). So instead of resolving, e.g., "wikileaks.bit" directly, you would resolve "wikileaks.bitname.org".
Of course, individual (traditional) domains are a target to censorship. But at the same time the community could "mirror" the namecoin domains under hundreds of different traditional domains. If a single domain goes down users can just switch to another domain. Alternatively, websites that expect such problems can in advance announce several alternative names (under domains such as "bitname.org").
I'm currently also looking for others to provide nameservers for the "bitname.org" domain. My goal is to have different nameservers operated by different individuals. If one of the nameservers needs to filter a particular result (due to local laws), it would then return "servfail" to the client, to allow the client to query another server instead.
The current prototype is using MaraDNS and a simple Python script that generates the zonefile from namecoin's JSON data. For the next "version" I'd like to write a custom DNS server (based on Python Twisted) that also supports the "translate" map method (which is currently not supported). In addition, with the current prototype there are some problems with "ns" entries, as the destination nameserver typically does not know what to do when the domain name is "bitname.org" instead of ".bit". I would be able to fix this issue by just proxying the query directly in my nameserver, however, this will only shift the problem to another layer, as, e.g., Web servers won't recognize "bitname.org" hostnames. Due to this issues I think that the typical usecase of "bitname.org" is to allow .bit users to make their sites available in the traditional DNS system, instead of providing a generic resolver for all ".bit" domain names.
Some further information is available on: http://bitname.org/
One issue with the current .bit TLD is adoption, as only a small subset of users will install/configure a custom resolver. Instead, I think it would be better (or at least a good alternative) to resolve namecoin names as subdomains of different "traditional" domains (such as "bitname.org"). So instead of resolving, e.g., "wikileaks.bit" directly, you would resolve "wikileaks.bitname.org".
Of course, individual (traditional) domains are a target to censorship. But at the same time the community could "mirror" the namecoin domains under hundreds of different traditional domains. If a single domain goes down users can just switch to another domain. Alternatively, websites that expect such problems can in advance announce several alternative names (under domains such as "bitname.org").
I'm currently also looking for others to provide nameservers for the "bitname.org" domain. My goal is to have different nameservers operated by different individuals. If one of the nameservers needs to filter a particular result (due to local laws), it would then return "servfail" to the client, to allow the client to query another server instead.
The current prototype is using MaraDNS and a simple Python script that generates the zonefile from namecoin's JSON data. For the next "version" I'd like to write a custom DNS server (based on Python Twisted) that also supports the "translate" map method (which is currently not supported). In addition, with the current prototype there are some problems with "ns" entries, as the destination nameserver typically does not know what to do when the domain name is "bitname.org" instead of ".bit". I would be able to fix this issue by just proxying the query directly in my nameserver, however, this will only shift the problem to another layer, as, e.g., Web servers won't recognize "bitname.org" hostnames. Due to this issues I think that the typical usecase of "bitname.org" is to allow .bit users to make their sites available in the traditional DNS system, instead of providing a generic resolver for all ".bit" domain names.
Some further information is available on: http://bitname.org/