services/Whois.md
... ...
@@ -32,10 +32,14 @@ Note that currently, most AS are using one of the legacy ASN range (and will pro
32 32
33 33
## DNS zones
34 34
35
-dn42 uses the `dn42.` TLD, which is not present in the root DNS zone of the ICANN-net. For details, see [DNS](/services/DNS).
35
+dn42 uses the `dn42.` TLD, which is not present in the root DNS zone of the ICANN-net. For details, see [DNS](/services/dns/Overview).
36 36
37 37
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).
38 38
39
+## Authentication
40
+
41
+See the page on [Registry Authentication](/howto/Registry-Authentication)
42
+
39 43
# Drone CI/CD
40 44
41 45
The gitea instance hosting the registry has an associated [Drone CI/CD](https://drone.io/) service:
... ...
@@ -44,21 +48,6 @@ The gitea instance hosting the registry has an associated [Drone CI/CD](https://
44 48
45 49
Users are free to add drone pipelines to their own repositories. Repositories can be enabled using the Drone server [user interface](https://drone.git.dn42/).
46 50
47
-# Telegram Bot
48
-A telegram whois bot owned by [@Oxygen233](https://t.me/oxygen233) is hosted on [@DN42WhoisBot](https://t.me/DN42WhoisBot).
49
-
50
-Privacy mode is enabled, please call the bot with @DN42WhoisBot when necessary.
51
-
52
-# Web interface and REST API
53
-
54
-<https://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.
55
-
56
-The service is provided by [dn42regsrv](https://git.burble.com/burble.dn42/dn42regsrv) which can also be run locally.
57
-
58
-## Authentication
59
-
60
-See the page on [Registry Authentication](/howto/Registry-Authentication)
61
-
62 51
# Whois daemons
63 52
64 53
**We have anycast IPv4 and IPv6, both reachable under whois.dn42. IPs are 172.22.0.43 respective fd42:d42:d42:43::1.**
... ...
@@ -77,7 +66,7 @@ Please consider joining these anycast adresses when you set up your server. Upda
77 66
| Bandura | whois.bandura.dn42 | 172.22.149.225 / fd04:234e:fc31::1 (may change in the future) |
78 67
| SUNNET | whois.sun.dn42 | 172.21.100.134 / fdc8:dc88:ee11:128::134 |
79 68
80
-## Down
69
+**Down**
81 70
82 71
| **person** | **dns** | **ip** |
83 72
|------------|---------------------------|-----------------|
... ...
@@ -125,6 +114,18 @@ cd whoisd/ruby
125 114
sudo ruby whoisd.rb nobody
126 115
```
127 116
117
+# Web interface and REST API
118
+
119
+<https://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.
120
+
121
+The service is provided by [dn42regsrv](https://git.burble.com/burble.dn42/dn42regsrv) which can also be run locally.
122
+
123
+# Telegram Bot
124
+
125
+A telegram whois bot owned by [@Oxygen233](https://t.me/oxygen233) is hosted on [@DN42WhoisBot](https://t.me/DN42WhoisBot).
126
+
127
+Privacy mode is enabled, please call the bot with @DN42WhoisBot when necessary.
128
+
128 129
# DNS interface
129 130
130 131
There is also a DNS-based interface to query AS information from the registry.