Services-DNS.md
... ...
@@ -5,7 +5,7 @@
5 5
6 6
## Using the DNS service
7 7
8
-You can either use the anycast resolver directly, or configure your local resolver to forward queries in the `.dn42` zone.
8
+Below are several ways to use the `dn42` DNS service, from easiest to more challenging. The recommended method is the second one.
9 9
10 10
### Using the anycast resolver directly
11 11
... ...
@@ -13,10 +13,18 @@ Please be aware that this method sends **all** your DNS queries (e.g. `google.co
13 13
14 14
To do this, just use `172.22.0.53` as your resolver, for instance in `/etc/resolv.conf`.
15 15
16
-### Forwarding `.dn42`queries
16
+### Forwarding `.dn42` queries to the anycast resolver
17 17
18 18
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]].
19 19
20
+### Recursive resolver
21
+
22
+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 [[Recursive DNS resolver]].
23
+
24
+### Building the dn42 zones from the registry
25
+
26
+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.
27
+
20 28
## Register a `.dn42` domain name
21 29
22 30
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).