services/DNS.md
... ...
@@ -1,51 +0,0 @@
1
-# DNS (DEPRECATED)
2
-**The new anycast resolver for `.dn42` runs on `172.23.0.53` and `fd42:d42:d42:53::1`. Please see [[Hierarchical DNS]] for more information.**
3
-
4
-**The information below is outdated.**
5
-***
6
-
7
-*(tl;dr)* We have a TLD for dn42, which is `.dn42`. The anycast resolver for `.dn42` runs on `172.23.0.53` and `fd42:d42:d42:53::1`.
8
-
9
-**DNS is build from [[whois database|services/Whois]]. So please edit your DNS-records there.**
10
-
11
-## Using the DNS service
12
-
13
-Below are several ways to use the `dn42` DNS service, from easiest to more challenging. The recommended method is the second one.
14
-
15
-### Using the anycast resolver directly
16
-
17
-Please be aware that this method sends **all** your DNS queries (e.g. `google.com`) to a random DNS server inside dn42. The server could fake the result and point you towards the russian mafia. They probably won't, but think about what you are doing. At the end of the day, your ISP could be evil as well, so it always boils down to a question of trust.
18
-
19
-To do this, just use `172.23.0.53` or `fd42:d42:d42:53::1` as your resolver, for instance in `/etc/resolv.conf`.
20
-
21
-### Forwarding `.dn42` queries to the anycast resolver
22
-
23
-If you run your own resolver (`unbound`, `dnsmasq`, `bind`), you can configure it to forward dn42 queries to the anycast DNS resolver. See [[DNS forwarder configuration|services/dns/Configuration]].
24
-
25
-### Recursive resolver
26
-
27
-You may also want to configure your resolver to recursively resolve dn42 domains. For this, you need to find authoritative DNS servers for the `dn42` zone (and for the reverse zones). See [[services/dns/Recursive DNS resolver]].
28
-
29
-### Building the dn42 zones from the registry
30
-
31
-Finally, you may want to host your own authoritative DNS server for the `dn42` zone and the reverse zones. The zone files are built from the monotone repository: scripts are provided in the repository itself.
32
-
33
-## Register a `.dn42` domain name
34
-
35
-The root zone for `dn42.` is built from the [[whois registry|services/Whois]]. If you want to register a domain name, you need to add it to the registry (of course, you also need one or two authoritative nameservers).
36
-
37
-There is a monitoring process that checks to verify that registered domain names are configured and reachable within the network. If a network has been detected as inactive consistently for a month, it will be moved to an offline folder in the registry. This will disable it from being generated into the anycast dns and future health checks. To reactivate the domain it will have to be moved back from the dns-offline folder.
38
-
39
-The health check results are emailed out each week to the mailing list.
40
-
41
-## DNS services for other networks
42
-
43
-Other networks are interconnected with dn42 (ChaosVPN, Freifunk, etc). Some of them also provide DNS service, you can configure your resolver to use it. See [[External DNS]].
44
-
45
-## Providing DNS services
46
-
47
-See [[Providing Anycast DNS]].
48
-
49
-## [[Hierarchical DNS]]
50
-
51
-This is a new effort to build a DNS system that mirrors how DNS was designed to work in clearnet.
... ...
\ No newline at end of file
services/Original-DNS-(deprecated).md
... ...
@@ -0,0 +1,51 @@
1
+# DNS (DEPRECATED)
2
+**The new anycast resolver for `.dn42` runs on `172.23.0.53` and `fd42:d42:d42:53::1`. Please see [[Hierarchical DNS]] for more information.**
3
+
4
+**The information below is outdated.**
5
+***
6
+
7
+*(tl;dr)* We have a TLD for dn42, which is `.dn42`. The anycast resolver for `.dn42` runs on `172.23.0.53` and `fd42:d42:d42:53::1`.
8
+
9
+**DNS is build from [[whois database|services/Whois]]. So please edit your DNS-records there.**
10
+
11
+## Using the DNS service
12
+
13
+Below are several ways to use the `dn42` DNS service, from easiest to more challenging. The recommended method is the second one.
14
+
15
+### Using the anycast resolver directly
16
+
17
+Please be aware that this method sends **all** your DNS queries (e.g. `google.com`) to a random DNS server inside dn42. The server could fake the result and point you towards the russian mafia. They probably won't, but think about what you are doing. At the end of the day, your ISP could be evil as well, so it always boils down to a question of trust.
18
+
19
+To do this, just use `172.23.0.53` or `fd42:d42:d42:53::1` as your resolver, for instance in `/etc/resolv.conf`.
20
+
21
+### Forwarding `.dn42` queries to the anycast resolver
22
+
23
+If you run your own resolver (`unbound`, `dnsmasq`, `bind`), you can configure it to forward dn42 queries to the anycast DNS resolver. See [[DNS forwarder configuration|services/dns/Configuration]].
24
+
25
+### Recursive resolver
26
+
27
+You may also want to configure your resolver to recursively resolve dn42 domains. For this, you need to find authoritative DNS servers for the `dn42` zone (and for the reverse zones). See [[services/dns/Recursive DNS resolver]].
28
+
29
+### Building the dn42 zones from the registry
30
+
31
+Finally, you may want to host your own authoritative DNS server for the `dn42` zone and the reverse zones. The zone files are built from the monotone repository: scripts are provided in the repository itself.
32
+
33
+## Register a `.dn42` domain name
34
+
35
+The root zone for `dn42.` is built from the [[whois registry|services/Whois]]. If you want to register a domain name, you need to add it to the registry (of course, you also need one or two authoritative nameservers).
36
+
37
+There is a monitoring process that checks to verify that registered domain names are configured and reachable within the network. If a network has been detected as inactive consistently for a month, it will be moved to an offline folder in the registry. This will disable it from being generated into the anycast dns and future health checks. To reactivate the domain it will have to be moved back from the dns-offline folder.
38
+
39
+The health check results are emailed out each week to the mailing list.
40
+
41
+## DNS services for other networks
42
+
43
+Other networks are interconnected with dn42 (ChaosVPN, Freifunk, etc). Some of them also provide DNS service, you can configure your resolver to use it. See [[External DNS]].
44
+
45
+## Providing DNS services
46
+
47
+See [[Providing Anycast DNS]].
48
+
49
+## [[Hierarchical DNS]]
50
+
51
+This is a new effort to build a DNS system that mirrors how DNS was designed to work in clearnet.
... ...
\ No newline at end of file