Updated Whois (markdown)

-For IPv6, we use ULA (that is, **fd00::/8**). Some participans also announce globally unique PI/PA address space, but these announcements are not accepted by most other participants. See also the [FAQ](/FAQ#frequently-asked-questions_what-about-ipv6-in-dn42).

-# Web interface

-[http://explorer.burble.dn42/](http://explorer.burble.dn42/) ([https://explorer.burble.com/](https://explorer.burble.com/) via clearnet) provides a web interface and REST API for querying the DN42 registry.

-A previous web interface hosted at Nixnodes, is no longer working. ([https://io.nixnodes.net/?registry](https://io.nixnodes.net/?registry]))

-To add or edit records with the web interface, authentication is done thanks to **maintainer objects**. Each maintainer object has a password associated to it.

-

-The password are not stored in cleartext in the registry: a hash is computed from the password and the name of the maintainer object. To generate such a hash (e.g. in case you forgot your password), use https://io.nixnodes.net/nctlio.php?m=dnr&gen=mypassword&mnt=MYMAINTAINER-MNT

-

-## REST API with JSON response

-

-Read-only, responses are encoded in JSON, for details please consult https://rest.dn42/ .

-

-## Misc

-

-A read-only interface is also available at http://ix.ucis.dn42/dn42/ ([public](http://ix.ucis.nl/dn42/) or 172.22.166.3). The used PHP scripts are available from UFO a.k.a. Ivo at request.

-# Address space

-

-There is nice 3djs visualisation showing current address space usage: http://dataviz.polynome.dn42/dn42-netblock-visu/registry.html ([public](http://dataviz.polyno.me/dn42-netblock-visu/registry.html) or 172.23.184.71). The input data is taken from the registry.

-

-Another visualisation shows the prefixes seen by BGP: http://dataviz.polynome.dn42/dn42-netblock-visu/index.html ([public](http://dataviz.polyno.me/dn42-netblock-visu/index.html) or 172.23.184.71).

-

-| nixnodes | whois.nixnodes.dn42 | 172.22.177.77 / fd42:1107::c0:e |

-| w0h | whois.w0h.dn42 | 172.22.232.6 / fd2d:a6da:8d1a:1408::6 |

-| Mic92 | whois.evenet.dn42 ([whois42d](https://git.dn42.us/dn42/whois42d)) | 172.23.75.1 / fd42:4992:6a6d::6 |

-| Fritz | whois.flhb.de | 172.22.70.69 / 2001:67c:708:102:5054:ff:fe57:9573 / fdd6:aff6:5f6f:102:5054:ff:fe57:9573 |

-

-# Monotone

-Monotone is an distributed revision control system. Monotone tracks revisions to files, groups sets of revisions into changesets, and tracks history across renames. The design principle is distributed operation making heavy use of cryptographic primitives to track file revisions (via the SHA-1 secure hash) and to authenticate user actions (via RSA cryptographic signatures). Each participant maintains their own revision history store in a local SQLite database. Monotone is especially strong in its support of a diverge/merge workflow, which it achieves in part by always allowing commit before merge. Revisions are exchanged using the custom netsync protocol which shares some conceptual ground with rsync and cvs.

- * [Website](http://monotone.ca/)

- * [Tutorial](http://monotone.ca/docs/Tutorial.html)

-

-## Monotone servers

-

-| Person | Address | Status |

-|----------|----------------------------------------|--------|

-| crest | mtn.crest.dn42 | UP |

-| siska | mtn.nixnodes.net (mtn.nixnodes.dn42) | UP |

-| dracoling | dn42.smrsh.net (net.smrsh.dn42) | UP |

-| xuu | mtn.xuu.dn42 (172.22.141.181) | UP |

-| zorun | mtn.polyno.me / mtn.polynome.dn42 (172.23.184.71)| UP |

-| Nurtic-Vibe | mtn.dn42.eu / mtn.grmml.dn42 (172.23.149.20/fd42:23:149:1::20)| UP |

-| toBee | mtn.mhm.dn42 (172.23.67.120)| UP |

-| hexa- | mtn.lossy.network (172.23.42.130) | UP |

-| tombii | mtn.tombii.dn42 (172.22.102.133) | UP |

-| Mic92 | mtn.evenet.dn42 (172.23.75.6/fd42:4992:6a6d::6) | UP |

-| weiti | mtn.weiti.dn42 (172.20.175.251/fdf7:17d5:de49::251) | UP |

-

-

-## Monotone branches

- * net.dn42.registry: Contains the registry and some related code

-

-## Client setup

-```sh

-mtn genkey [email protected]

-mtn pubkey [email protected] # send the output to some $monotone_server operator (do NOT send the keypair!)

-mtn clone 'mtn://$monotone_server/?net.dn42.*' --branch net.dn42.registry

-cd net.dn42.registry

-$add_your_objects

-mtn add --unknown

-mtn ci -k [email protected]

-mtn sync

-```

-

-## Server setup

-

-Debian has a package "monotone-server", with config located in "/etc/monotone".

-

-### Allowing somebody to write to a monotone server

-

-If you want to allow somebody else to write to your monotone server (for instance for somebody to sync with you), you first need to import their key, here on Debian:

-

- mtn --db /var/lib/monotone/default.mtn read < pubkey

-

-Then edit the file `write-permissions` (`/etc/monotone/write-permissions` on Debian) to add the email address associated with the public key.

-

-References: http://www.monotone.ca/docs/Basic-Network-Service.html#Basic-Network-Service and https://geti2p.net/en/get-involved/guides/monotone#obtaining-and-deploying-developers-keys

-

-### Tips and tricks

-

-Pro-tip: monotone seems to use `SO_V6ONLY`, which is annoying. To bind to both IPv4 and IPv6, use `ADDRESS=":: --bind 0.0.0.0"` in `/etc/default/monotone`.