f9b7ce4425f8c4131b4eb885ea6ece1b26d6f6e8
services/Original-DNS-(deprecated).md
... | ... | @@ -3,7 +3,7 @@ This information is now **deprecated**. Please check [[New DNS]] for the current |
3 | 3 | |
4 | 4 | *** |
5 | 5 | |
6 | -*(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`. At the date March 27 2020, these server are **not working** anymore. |
|
6 | +*(tl;dr)* We have a TLD for dn42, which is `.dn42`. The anycast resolver for `.dn42` runs on `172.20.0.53` and `fd42:d42:d42:54::1`. |
|
7 | 7 | |
8 | 8 | **DNS is build from [[whois database|services/Whois]]. So please edit your DNS-records there.** |
9 | 9 | |
... | ... | @@ -15,7 +15,7 @@ Below are several ways to use the `dn42` DNS service, from easiest to more chall |
15 | 15 | |
16 | 16 | 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. |
17 | 17 | |
18 | -To do this, just use `172.23.0.53` or `fd42:d42:d42:53::1` as your resolver, for instance in `/etc/resolv.conf`. |
|
18 | +To do this, just use `172.20.0.53` or `fd42:d42:d42:54::1` as your resolver, for instance in `/etc/resolv.conf`. |
|
19 | 19 | |
20 | 20 | ### Forwarding `.dn42` queries to the anycast resolver |
21 | 21 |