Updated Whois (markdown)

* Subnet assignations

* DNS root zone for `dn42.`

dn42 uses some names and numbers, which are declared in the registry. Whenever possible, we try to stick to names and numbers that do not conflict with the ICANN-net or other networks similar to dn42, for instance by using private numbers space.

dn42 uses **172.22.0.0/15** for IPv4.

For IPv6, we use both ULA (that is, **fd00::/8**) and globally unique PI/PA address space of participants. ULA is prefered for various reasons, see the [FAQ](/FAQ#What-about-IPv6-in-DN42?).

Since June 2014, dn42 is using the **4242420000-4242429999** ASN range for allocations. This range is further subdivided:

* **4242420000-4242423999** for end-users allocations

Note that currently, most AS are using one of the legacy ASN range (and will probably continue to do so, as renumbering is painful). See the [FAQ](/FAQ#Why-are-you-using-ASN-in-the-76100-76199-range?) for a discussion on AS ranges.

dn42 uses the `dn42.` TLD, which is not present in the root DNS zone of the ICANN-net. For details, see [[DNS]].

Note that other TLDs should also be usable from dn42, most notably from Freifunk and ChaosVPN. A tentative list is available at [External DNS](/services/dns/External-DNS).

Nixnodes provides a nice web interface, that allows you to **add/edit records** easily. It is available at https://io.nixnodes.net/?registry. A full guide is available at [Getting started](/Getting-started#Fill-in-the-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

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.

There is also a DNS-based interface to query AS information from the registry. The DNS zone is `asn.dn42`. Example:

The idea comes from the guys at cymru.com, who provide this service for the Internet (e.g. `AS1.asn.cymru.com`), see https://www.team-cymru.org/Services/ip-to-asn.html#dns

There is nice 3djs visualisation showing current address space usage: http://dataviz.polynome.dn42/dn42-netblock-visu/registry.html ([public](http://109.24.208.244:8888/dn42-netblock-visu/registry.html) or 172.23.184.98). 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://109.24.208.244:8888/dn42-netblock-visu/index.html) or 172.23.184.98).

* [[lglass]] is a python implementation for working with the registry. It features a whois server, tools to manipulate the data (DNS zone generation, etc).

We have anycast IPv4 and IPv6, both reachable under whois.dn42. IPs are 172.22.0.43 respective fd42:d42:d42:43::1. Please consider joining these anycast-adresses when you setup your server. Updates every 1 hour would be nice for a start.

| nixnodes | whois.nixnodes.dn42 | 172.22.177.77 |

| prauscher | sheldon.prauscher.dn42 | 172.22.120.1 |

```sh

whois -h $host $query

```

```sh

$ cat /etc/whois.conf

You can then use whois without specifying the server. Works at least with Marco d'Itri's whois client.

```sh

cd /home/some/path/to/store/branch

sudo aptitude install ruby rubygems

sudo ruby whoisd.rb nobody

```

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)

| Person | Address | Status |

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

| xuu | mtn.xuu.dn42 (172.22.141.131) | UP |

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

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

```sh

mtn genkey [email protected]

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

mtn sync

```

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