services/DNS.md
... ...
@@ -4,7 +4,7 @@
4 4
**The information below is outdated.**
5 5
***
6 6
7
-*(tl;dr)* We have a TLD for dn42, which is `.dn42`. The anycast resolver for `.dn42` runs on `172.22.0.53` and `fd42:d42:d42:53::1`.
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 8
9 9
**DNS is build from [[whois database|services/Whois]]. So please edit your DNS-records there.**
10 10
... ...
@@ -16,7 +16,7 @@ Below are several ways to use the `dn42` DNS service, from easiest to more chall
16 16
17 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 18
19
-To do this, just use `172.22.0.53` or `fd42:d42:d42:53::1` as your resolver, for instance in `/etc/resolv.conf`.
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 20
21 21
### Forwarding `.dn42` queries to the anycast resolver
22 22