3401df11fcee58da75e136b12775857422710ef4
Services-Whois.md
| ... | ... | @@ -1,6 +1,19 @@ |
| 1 | 1 | # Whois registry |
| 2 | 2 | **aka** _The registry_. |
| 3 | 3 | |
| 4 | +The registry contains: |
|
| 5 | + |
|
| 6 | + * AS numbers assignations |
|
| 7 | + * Subnet assignations |
|
| 8 | + * DNS root zone for `dn42.` |
|
| 9 | + |
|
| 10 | +## Web interface |
|
| 11 | + |
|
| 12 | +Nixnodes provides a nice web interface, that allows you to **add/edit records** easily. It is available at https://io.nixnodes.net/?registry. To add records, you must first create a maintainer object. |
|
| 13 | + |
|
| 14 | +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. |
|
| 15 | + |
|
| 16 | + |
|
| 4 | 17 | ## Whois daemons |
| 5 | 18 | * welterde: thinkbase.srv.welterde.de (46.4.248.201) |
| 6 | 19 | * fritz: whois.fritz.dn42 (172.22.119.139) |
| ... | ... | @@ -20,15 +33,6 @@ cd whoisd/ruby |
| 20 | 33 | sudo ruby whoisd.rb nobody |
| 21 | 34 | ``` |
| 22 | 35 | |
| 23 | -## Web access |
|
| 24 | -* NixNodes: https://io.nixnodes.net/dn42/registry - registry browser/editor (beta) |
|
| 25 | - |
|
| 26 | -* UFO: http://ix.ucis.dn42/dn42/ ([public](http://ix.ucis.nl/dn42/) or 172.22.166.3) (read only)<br> |
|
| 27 | - The used PHP scripts are available from UFO a.k.a. Ivo at request. |
|
| 28 | - |
|
| 29 | - |
|
| 30 | - |
|
| 31 | - |
|
| 32 | 36 | |
| 33 | 37 | ## Monotone |
| 34 | 38 | 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. |