[ANN] NamecoinControl - Manage namecoin services

[khal]

A first version of the resolver for .bit has been committed.

What is supported :
- ip, ip6, tor, i2p, freenet, fingerprint records
- in root zone, sub-domains (any level) and "*" sub-domain using map
- fingerprint is searched in sub-domains up to the root (a root fingerprint will be valid for the whole zone, no need to add "map{*: {fingerprint: XXX}}" )
- legacy support for "" instead of "ip"
- "" used in map instead of root zone [edit: added]

Not supported yet :
- "" used in map instead of root zone [edit: now supported]
- ns, import, alias, translate, delegate, etc records

./nmcontrol.py dns getFingerprint dot-bit.bit
["30:B0:60:94:32:08:EC:F5:BE:DF:F4:BB:EE:52:90:2C:5D:47:62:46"]

./nmcontrol.py dns getIp4 1.bit
"212.232.51.96"

No support of "" used in map instead of root zone :

./nmcontrol.py dns getIp4 ns.bit
[]

[EDIT]Added support of "" used in map instead of root zone :

./nmcontrol.py dns getIp4 ns.bit
["10.0.0.0"]

[biolizard89]

Nice work khal, I'll try it out when I have a few minutes of downtime. I'll also see if I can get Convergence to work with the new API calls.

[khal]

Nice work khal, I'll try it out when I have a few minutes of downtime. I'll also see if I can get Convergence to work with the new API calls.

I can not wait to see it :p

I've also added support of "alias" in the last commits and changed the way methods are called in the software.
So, rpc calls may have changed too (it should not change when called from external)

I still need to re-add support for non .bit domains with the new pluginDNS and add support for ns.

Then the DNS server will switch to this new plugin (It still uses the old system, or may even be broken [I've not tested it since 0.8 :p])

[khal]

Help has been fixed and sub-domains do not return ip of their parent domains anymore :p.

One exception is for fingerprint : a fingerprint in a parent record can be returned for any of its subdomains.
A single fingerprint needs to be put in the root of the json, a second record in not needed in 'map{*: fingerprint:"xx"}'
Of course, if a different fingerprint is set for one sub-domain, it'll have the priority over the parent fingerprint.

[khal]

A new RPC command is available : getJson.
It allows to extract the json record by giving the json path (keys) to the record.
The result will always be valid json data.

Code: Select all

./nmcontrol.py data getJson d/dot-bit help
Get the json record for specified keys
getJson <name> <key1,key2,key3,...>

Exemple :

Code: Select all

./nmcontrol.py data getJson d/dot-bit info,description
"Dot-BIT Project - Official Website"

Normal record (truncated) to understand where the result is extracted from :

Code: Select all

./nmcontrol.py data getValue d/dot-bit
{"[b]info[/b]":{"[b]description[/b]":"Dot-BIT Project - Official Website","registrar":"http://register.dot-bit.org"}}

Source : https://github.com/khalahan/nmcontrol

[khal]

The DNS server of NamecoinControl is now fixed.
It uses both the new API (getIp4, getIp6, etc) and old code as a fall back.

Thanks to uVAdN2vUw2aMENSu19cY7ic24Gvp7Fd.

[phelix]

I was wondering if this was enough to go fully independent and from the code it looks like it is.

No need for Acrylic/polipo any more as NMControl will forward non .bit requests. Nice.

[biolizard89]

Excellent work khal, I'll try this out when I have a few minutes. @phelix, keep in mind that proxies still have one advantage over DNS server implementations: proxies can handle Onion and I2P resolution for .bit domains, while standard DNS servers will only be able to handle IPv4 and IPv6. Not a huge deal for most applications, but for people who need Onion and I2P to work, proxies are the way to go. (When I get some downtime I'm going to try to get Convergence working with Onion/I2P... but I'm not sure when that'll be.)

[phelix]

I played a little with a http GUI. Sources: http://blockchained.com/stuff/nmctrl_ht ... estion.zip

It does not do much and is completely separate but IMHO something like this would be nice for nmctrl.

As khal suggested we could use a local tld like namecoin or nmctrl instead of 127.0.0.1

[Pagel1928]

I just want to point out my pull request here:

https://github.com/khalahan/nmcontrol/pull/3

This fixes up the nmcontrol DNS server so it handles subdomains properly.

Additionally it implements .tor lookups, which return the onion address as a CNAME:

dig lolicore.tor
lolicore.tor. 5 IN CNAME lolicore75rq3tm5.onion.

I'm wondering what is the right way this should actually be done? From here it would be relatively easy to do this lookup/resolution with a browser plugin.

Additionally I quite prefer the format .tor.bit and .ip4.bit, so perhaps I should implement it that way instead...