From 31e46a2011b9b463c105527751a2552328c1e918 Mon Sep 17 00:00:00 2001 From: Simon Marsh Date: Sun, 30 May 2021 20:35:15 +0000 Subject: [PATCH] Replace wikilink style links with generic markdown --- FAQ.md | 4 -- Home.md | 6 +-- _Sidebar.md | 72 ++++++++++++------------- contact.md | 4 +- howto/EdgeOS-Config.md | 4 +- howto/Edgeos-Config-Example-number-2.md | 4 +- howto/OpenWRT.md | 2 +- howto/ROA-slash-RPKI.md | 2 - internal/Internal-Services.md | 6 +-- services/DNS.md | 16 +++--- services/Distributed-Wiki.md | 2 +- services/New-DNS.md | 14 ++--- services/Old-Hierarchical-DNS.md | 2 +- services/Original-DNS-(deprecated).md | 16 +++--- services/Route-Collector.md | 2 +- services/Whois.md | 4 +- services/dns/External-DNS.md | 2 +- services/dns/Providing-Anycast-DNS.md | 2 +- services/dns/Recursive-DNS-resolver.md | 2 +- 19 files changed, 80 insertions(+), 86 deletions(-) diff --git a/FAQ.md b/FAQ.md index 1f7e340..314719b 100644 --- a/FAQ.md +++ b/FAQ.md @@ -1,7 +1,3 @@ -# Frequently Asked Questions - -[[_TOC_]] - ### How do I connect to DN42? diff --git a/Home.md b/Home.md index 751258d..5c038e5 100644 --- a/Home.md +++ b/Home.md @@ -4,7 +4,7 @@ dn42 is a big dynamic [VPN](http://en.wikipedia.org/wiki/Virtual_private_network A number of services are provided on the network: see [internal](/internal/Internal-Services) (only available from within dn42). Also, dn42 is interconnected with other networks, such as [ChaosVPN](http://wiki.hamburg.ccc.de/ChaosVPN) or some [Freifunk](http://en.wikipedia.org/wiki/Freifunk) networks. -Still have questions? We have [[FAQs|FAQ]] listed. +Still have questions? We have [FAQs](/FAQ) listed. ## Why dn42? @@ -30,9 +30,9 @@ If your hackerspace is actually using dn42 to provide some services, please let ## Join or Contact us -dn42 is operated by a group of volunteers. There is no central authority which controls or impersonates the network. Take a look at the [[contact]] page to see how to collaborate or contact us. +dn42 is operated by a group of volunteers. There is no central authority which controls or impersonates the network. Take a look at the [contact](/contact) page to see how to collaborate or contact us. -The [[Getting started|howto/Getting-Started]] page helps you to get your first node inside the network. +The [Getting started](/howto/Getting-Started) page helps you to get your first node inside the network. ## External resources about dn42 diff --git a/_Sidebar.md b/_Sidebar.md index 6759574..d514427 100644 --- a/_Sidebar.md +++ b/_Sidebar.md @@ -1,49 +1,49 @@
Site Links
- * [[Home]] - * [[Getting Started|howto/Getting-Started]] - * [[Registry Authentication|howto/Registry-Authentication]] - * [[Address Space|howto/Address-Space]] - * [[FAQ|/FAQ]] + * [Home](/Home) + * [Getting Started](/howto/Getting-Started) + * [Registry Authentication](/howto/Registry-Authentication) + * [Address Space](/howto/Address-Space) + * [FAQ](//FAQ) * How-To - * [[Wireguard|howto/wireguard]] - * [[Openvpn|howto/openvpn]] - * [[IPsec With Public Keys|howto/IPsec-with-PublicKeys]] - * [[Tinc|howto/tinc]] - * [[GRE on FreeBSD|howto/GRE-on-FreeBSD]] - * [[GRE on OpenBSD|howto/GRE-on-OpenBSD]] - * [[IPv6 Multicast (PIM-SM)|howto/IPv6-Multicast]] - * [[Bird|howto/Bird]] / [[Bird2|howto/Bird2]] - * [[Quagga|howto/Quagga]] - * [[OpenBGPD|howto/OpenBGPD]] - * [[Mikrotik RouterOS|howto/mikrotik]] - * [[EdgeRouter|howto/EdgeOS-Config]] - * [[Static routes on Windows|howto/Static-routes-on-Windows]] - * [[Universal Network Requirements|howto/networksettings]] - * [[VyOS|howto/vyos]] + * [Wireguard](/howto/wireguard) + * [Openvpn](/howto/openvpn) + * [IPsec With Public Keys](/howto/IPsec-with-PublicKeys) + * [Tinc](/howto/tinc) + * [GRE on FreeBSD](/howto/GRE-on-FreeBSD) + * [GRE on OpenBSD](/howto/GRE-on-OpenBSD) + * [IPv6 Multicast (PIM-SM)](/howto/IPv6-Multicast) + * [Bird](/howto/Bird) / [Bird2](/howto/Bird2) + * [Quagga](/howto/Quagga) + * [OpenBGPD](/howto/OpenBGPD) + * [Mikrotik RouterOS](/howto/mikrotik) + * [EdgeRouter](/howto/EdgeOS-Config) + * [Static routes on Windows](/howto/Static-routes-on-Windows) + * [Universal Network Requirements](/howto/networksettings) + * [VyOS](/howto/vyos) * Services - * [[IRC|services/IRC]] - * [[Whois registry|services/Whois]] - * [[DNS|services/DNS]] - * [[Public DNS|services/Clearnet-Domains]] - * [[Looking Glasses|services/Looking-Glasses]] - * [[Repository Mirrors|services/Repository-Mirrors]] - * [[Distributed Wiki|services/Distributed-Wiki]] - * [[Certificate Authority|services/Certificate-Authority]] - * [[Route Collector|services/Route-Collector]] + * [IRC](/services/IRC) + * [Whois registry](/services/Whois) + * [DNS](/services/DNS) + * [Public DNS](/services/Clearnet-Domains) + * [Looking Glasses](/services/Looking-Glasses) + * [Repository Mirrors](/services/Repository-Mirrors) + * [Distributed Wiki](/services/Distributed-Wiki) + * [Certificate Authority](/services/Certificate-Authority) + * [Route Collector](/services/Route-Collector) * Internal - * [[Internal services|internal/Internal-Services]] - * [[Interconnections|internal/Interconnections]] - * [[APIs|internal/APIs]] - * [[Historical services|internal/Historical-Services]] + * [Internal services](/internal/Internal-Services) + * [Interconnections](/internal/Interconnections) + * [APIs](/internal/APIs) + * [Historical services](/internal/Historical-Services) * External Tools - * [[Paste Board|https://paste.dn42.us]] - * [[Git Repositories|https://git.dn42.dev]] + * [Paste Board](/https://paste.dn42.us) + * [Git Repositories](/https://git.dn42.dev) -------------- -[[_TOC_]] \ No newline at end of file +[[_TOC_]] diff --git a/contact.md b/contact.md index aff7548..98e41cc 100644 --- a/contact.md +++ b/contact.md @@ -2,7 +2,7 @@ Members of the dn42 network mostly communicate via IRC or the mailing list. -If you would like to contact an individual network operator, you will find contact information in the [[Whois]] registry. +If you would like to contact an individual network operator, you will find contact information in the [Whois](/Whois) registry. ## Mailing list @@ -15,7 +15,7 @@ If you would like to contact an individual network operator, you will find conta Channel #dn42 in [hackint](http://www.hackint.eu/) -See [[IRC]] too. +See [IRC](/IRC) too. ## Twitter diff --git a/howto/EdgeOS-Config.md b/howto/EdgeOS-Config.md index fe03bc2..e6c2cfe 100644 --- a/howto/EdgeOS-Config.md +++ b/howto/EdgeOS-Config.md @@ -11,8 +11,8 @@ This document describes some possibilities for connecting to dn42 using an Ubiqu ## First Steps -1. Create the required objects in the Registry - see [[Getting started]] -2. Find a peer - ask nicely in [[IRC]]! +1. Create the required objects in the Registry - see [Getting Started](/Getting-Started) +2. Find a peer - ask nicely in [IRC](/IRC)! 3. Get the following details: * Tunnel configuration (OpenVPN, IPsec, QuickTun) * AS numbers diff --git a/howto/Edgeos-Config-Example-number-2.md b/howto/Edgeos-Config-Example-number-2.md index 8361994..3725042 100644 --- a/howto/Edgeos-Config-Example-number-2.md +++ b/howto/Edgeos-Config-Example-number-2.md @@ -14,9 +14,9 @@ Also thanx to drathir for his patience and support * Basic EdgeOS knowledge is required -1) you need to create all required fields in the registry --> look at [[Getting started]] page +1) you need to create all required fields in the registry --> look at [Getting Started](/Getting-Started) page -2) get a peer --> ask nice @ [[IRC]] +2) get a peer --> ask nice @ [IRC](/IRC) 3) You need following data from the peer diff --git a/howto/OpenWRT.md b/howto/OpenWRT.md index 8183364..d838987 100644 --- a/howto/OpenWRT.md +++ b/howto/OpenWRT.md @@ -80,4 +80,4 @@ You have to use this patch: https://dev.openwrt.org/changeset/35484 (monkeypatch ## DNS -See [[DNS Configuration|/services/dns/Configuration]]. This will use the anycast dn42 DNS server to resolve `dn42` and relevant reverse domains. \ No newline at end of file +See [DNS Configuration](/services/dns/Configuration). This will use the anycast dn42 DNS server to resolve `dn42` and relevant reverse domains. \ No newline at end of file diff --git a/howto/ROA-slash-RPKI.md b/howto/ROA-slash-RPKI.md index a2c30b1..f526021 100644 --- a/howto/ROA-slash-RPKI.md +++ b/howto/ROA-slash-RPKI.md @@ -1,5 +1,3 @@ -[[_TOC_]] - ## What is ROA? diff --git a/internal/Internal-Services.md b/internal/Internal-Services.md index 7d0c9be..9511f99 100644 --- a/internal/Internal-Services.md +++ b/internal/Internal-Services.md @@ -6,12 +6,12 @@ You are asked to show some creativity in terms of network usage and content. ;) ## CA -xuu is maintaining an [[certificate authority|/services/Certificate-Authority]] for internal services. +xuu is maintaining an [certificate authority](/services/Certificate-Authority) for internal services. zotan is maintaining an (experimental, but working) [ACME server](https://acme.dn42) (with accompanying CA), compatible with any LetsEncrypt client like Certbot, Dehydrated or Caddy. ## Network-related - * See [[Looking Glasses|/services/Looking-Glasses]] for more network diagnostic tools + * See [Looking Glasses](/services/Looking-Glasses) for more network diagnostic tools * Realtime network map: [map.dn42](http://map.dn42/) (DN42) or [map42.0x7f.cc](https://map42.0x7f.cc) (IANA) _(Note: This is a direct copy of nixnodes map with some fixes and new functions since original map is no longer get maintained. This map is currently using MRT dump from GRC as source. We will pull new dumps from GRC every 15 minutes.)_ * Network Information Service: [info.nia.dn42](http://info.nia.dn42) (DN42) or [bgp42.strexp.net](https://bgp42.strexp.net) (IANA). Main functions including _network information_, _network map (from map.dn42, require WebGL)_, _network ranking (based on centrality)_, _ROA alerting_ and _path finder_. * Yet Another WIP network map: [map.jerry.dn42](https://map.jerry.dn42/) (via DN42) or [map.meson.cc](https://map.meson.cc) (via clearnet) _(uses MRT dump as source, updated every 30 minutes.)_ @@ -101,7 +101,7 @@ Some [Advanced Direct Connect](https://en.wikipedia.org/wiki/Advanced_Direct_Con ### Tor -Entry points to the Tor network are available on dn42. See [[Tor|internal/services/Tor]] for more details. +Entry points to the Tor network are available on dn42. See [Tor](/internal/services/Tor) for more details. ### Telegram diff --git a/services/DNS.md b/services/DNS.md index c640c56..4641aac 100644 --- a/services/DNS.md +++ b/services/DNS.md @@ -48,22 +48,22 @@ search dn42 There are multiple top level domains (TLDs) associated with DN42, its affiliated networks and for reverse DNS that must be configured in order to run your own resolver. The registry is the authoritative source of active TLDs, but see also -this page [[dns/External-DNS|/services/dns/External-DNS]] in the wiki. +this page [dns/External-DNS](/services/dns/External-DNS) in the wiki. ### Split horizon DNS In this configuration, you run your own, caching resolver but forward DN42 related queries (with recursion bit set) -to the anycast service. Example configurations for different recursor implementations are included in the [[dns/Configuration|/services/dns/Configuration]] page. +to the anycast service. Example configurations for different recursor implementations are included in the [dns/Configuration](/services/dns/Configuration) page. ### Full recursion Authoritative DNS for DN42 is provided by the *.delegation-servers.dn42 servers, see the DNS architecture here -[[New DNS|New-DNS]] Delegations servers have full support for DNSSEC. +[New DNS](/New-DNS) Delegations servers have full support for DNSSEC. ## Further Information -* [[dns/Configuration|/services/dns/Configuration]] - Forwarder configuration examples -* [[New DNS|New-DNS]] - current architecture -* [[dns/External-DNS|/services/dns/External-DNS]] - external DNS zones from interconnected networks -* [[Old Hierarchical DNS|Old-Hierarchical-DNS]] - deprecated -* [[Original DNS (deprecated)|Original-DNS-(deprecated)]] - deprecated +* [dns/Configuration](/services/dns/Configuration) - Forwarder configuration examples +* [New DNS](/New-DNS) - current architecture +* [dns/External-DNS](/services/dns/External-DNS) - external DNS zones from interconnected networks +* [Old Hierarchical DNS](/Old-Hierarchical-DNS) - deprecated +* [Original DNS (deprecated)](/Original-DNS-(deprecated)) - deprecated diff --git a/services/Distributed-Wiki.md b/services/Distributed-Wiki.md index 7ea06bf..a7fb78d 100644 --- a/services/Distributed-Wiki.md +++ b/services/Distributed-Wiki.md @@ -1,5 +1,5 @@ The idea is to deploy mirrors across dn42 using [anycast](https://en.wikipedia.org/wiki/Anycast) addressing (BGP), thus providing redundancy, load-balancing and improved access times to the wiki. Sites are powered by [gollum](https://github.com/gollum/gollum) which has no native SSL support, so Nginx acts as a reverse proxy and handles the encryption. -The local webserver is monitored with a simple [[shell script|Distributed-Wiki#exabgp_watchdog-script]] working [[in conjunction|Distributed-Wiki#exabgp]] with [ExaBGP](https://github.com/Exa-Networks/exabgp), announcing/withdrawing the assigned route if the service is up/down. +The local webserver is monitored with a simple [shell script](/Distributed-Wiki#exabgp_watchdog-script) working [in conjunction](/Distributed-Wiki#exabgp) with [ExaBGP](https://github.com/Exa-Networks/exabgp), announcing/withdrawing the assigned route if the service is up/down. ## Prerequisites diff --git a/services/New-DNS.md b/services/New-DNS.md index ddf870e..79f90c2 100644 --- a/services/New-DNS.md +++ b/services/New-DNS.md @@ -1,10 +1,10 @@ -After frequent issues with the [[Old Hierarchical DNS|Old-Hierarchical-DNS]] system in early 2018, work has started to build a new and more reliable DNS system. The main goals are: +After frequent issues with the [Old Hierarchical DNS](/Old-Hierarchical-DNS) system in early 2018, work has started to build a new and more reliable DNS system. The main goals are: * Reliability and Consistency to avoid debugging very obscure issues that are also hard to reproduce. * Low maintenance burden on operators. * Proper DNSSEC support for everything. # End Users -It is **strongly recommended** to run your own resolver for security and privacy reasons. Setting it up and maintaining it should be easy, see [[services/dns/Configuration|services/dns/Configuration]]. +It is **strongly recommended** to run your own resolver for security and privacy reasons. Setting it up and maintaining it should be easy, see [services/dns/Configuration](/services/dns/Configuration). If running your own resolver is not possible or undesirable, you can choose one or more instances from [dns/recursive-servers.dn42 in the registry](https://git.dn42.us/dn42/registry/src/master/data/dns/recursive-servers.dn42). Please make sure you fully understand the consequences and fully trust these operators. @@ -25,9 +25,9 @@ These are simple authoritative servers for the dn42 zone, rDNS and a few DNS inf These instances do not serve any clients. They poll the registry regularly and rebuild and resign (DNSSEC) the zones as needed. If any zone changes, all *.delegation-servers.dn42 instances are notified ([RFC1996](https://tools.ietf.org/html/rfc1996)) which then load the new zone data over AXFR ([RFC5936](https://tools.ietf.org/html/rfc5936)). The pool of masters is intentionally kept very small because of its much higher coordination needs and also the lacking support of a multi-master mode in many authoritative server implementations. The masters are only reachable over dedicated IPv6 assignments which are set up in a way that any master operator can hijack the address of a problematic master without having to wait for its operator to fix something. # Running your own instances -* If you want to run your own instances, make sure you are subscribed to the [[mailinglist|/contact]]. It is also strongly recommended to join #dn42-dns@hackint. All changes are announced to the mailinglist but IRC makes debugging sessions much easier. +* If you want to run your own instances, make sure you are subscribed to the [mailinglist](//contact). It is also strongly recommended to join #dn42-dns@hackint. All changes are announced to the mailinglist but IRC makes debugging sessions much easier. * Choose the implementation(s) you want to use. It should support at least AXFR+NOTIFY (*.delegation-servers.dn42) or DNSSEC (*.recursive-servers.dn42). -* Check if [[TODO|TODO]] already has configuration snippets for your implementation. +* Check if [TODO](/TODO) already has configuration snippets for your implementation. * If yes, download it from there and include it in the main configuration. * If not, then join us in #dn42-dns@hackint so we can add it together. * Verify that everything works: @@ -47,6 +47,6 @@ The set of valid KSKs can be found in the registry. # See also -* [[DNS Quick Start|DNS]] -* [[Old Hierarchical DNS|Old-Hierarchical-DNS]] -* [[Original DNS (deprecated)|Original-DNS-(deprecated)]] \ No newline at end of file +* [DNS Quick Start](/DNS) +* [Old Hierarchical DNS](/Old-Hierarchical-DNS) +* [Original DNS (deprecated)](/Original-DNS-(deprecated)) \ No newline at end of file diff --git a/services/Old-Hierarchical-DNS.md b/services/Old-Hierarchical-DNS.md index 92e1d2b..3d8c1f0 100644 --- a/services/Old-Hierarchical-DNS.md +++ b/services/Old-Hierarchical-DNS.md @@ -1,4 +1,4 @@ -This information is now **deprecated**. Please check [[New DNS]] for the current architecture. +This information is now **deprecated**. Please check [New DNS](/New DNS) for the current architecture. *** diff --git a/services/Original-DNS-(deprecated).md b/services/Original-DNS-(deprecated).md index f16591a..c7bca38 100644 --- a/services/Original-DNS-(deprecated).md +++ b/services/Original-DNS-(deprecated).md @@ -1,11 +1,11 @@ # Original DNS (deprecated) -This information is now **deprecated**. Please check [[New DNS]] for the current architecture. +This information is now **deprecated**. Please check [New DNS](/New DNS) for the current architecture. *** *(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`. -**DNS is build from [[whois database|services/Whois]]. So please edit your DNS-records there.** +**DNS is build from [whois database](/services/Whois). So please edit your DNS-records there.** ## Using the DNS service @@ -19,11 +19,11 @@ To do this, just use `172.20.0.53` or `fd42:d42:d42:54::1` as your resolver, for ### Forwarding `.dn42` queries to the anycast resolver -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]]. +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). ### Recursive resolver -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]]. +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](/services/dns/Recursive DNS resolver). ### Building the dn42 zones from the registry @@ -31,16 +31,16 @@ Finally, you may want to host your own authoritative DNS server for the `dn42` z ## Register a `.dn42` domain name -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). +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). ## DNS services for other networks -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]]. +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](/External DNS). ## Providing DNS services -See [[Providing Anycast DNS]]. +See [Providing Anycast DNS](/Providing Anycast DNS). -## [[Old Hierarchical DNS]] +## [Old Hierarchical DNS](/Old Hierarchical DNS) 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 diff --git a/services/Route-Collector.md b/services/Route-Collector.md index c6bb065..a3c214e 100644 --- a/services/Route-Collector.md +++ b/services/Route-Collector.md @@ -4,7 +4,7 @@ The Global Route Collector (GRC) provides a real time view of routing and peerin Technically the GRC is a [bird](https://bird.network.cz/) instance that anyone can peer with, it imports all routes whilst exporting none and provides a number of interfaces for querying the route data. -Data from the GRC is used to generate some of the DN42 Maps (see the [[Internal Services|/internal/Internal-Services]] page). +Data from the GRC is used to generate some of the DN42 Maps (see the [Internal Services](//internal/Internal-Services) page). ## Peering with the collector diff --git a/services/Whois.md b/services/Whois.md index e29ad64..5cc8e7d 100644 --- a/services/Whois.md +++ b/services/Whois.md @@ -32,7 +32,7 @@ Note that currently, most AS are using one of the legacy ASN range (and will pro ## DNS zones -dn42 uses the `dn42.` TLD, which is not present in the root DNS zone of the ICANN-net. For details, see [[DNS]]. +dn42 uses the `dn42.` TLD, which is not present in the root DNS zone of the ICANN-net. For details, see [DNS](/DNS). 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). @@ -75,7 +75,7 @@ The idea comes from the guys at cymru.com, who provide this service for the Inte # Software - * [[lglass|internal/lglass]] is a python implementation for working with the registry. It features a whois server, tools to manipulate the data (DNS zone generation, etc). + * [lglass](/internal/lglass) is a python implementation for working with the registry. It features a whois server, tools to manipulate the data (DNS zone generation, etc). * [whois42d](https://github.com/dn42/whois42d) written in golang, lightweight/fast, whois server with support for all registry objects, type filtering and systemd socket activation. # Whois daemons diff --git a/services/dns/External-DNS.md b/services/dns/External-DNS.md index f74adcd..8d70e8c 100644 --- a/services/dns/External-DNS.md +++ b/services/dns/External-DNS.md @@ -31,4 +31,4 @@ NeoNetwork zone files can be found here: https://github.com/NeoCloud/NeoNetwork/ ## Configuration -See [[DNS forwarding configuration|/services/dns/Configuration]]. \ No newline at end of file +See [DNS forwarding configuration](/services/dns/Configuration). \ No newline at end of file diff --git a/services/dns/Providing-Anycast-DNS.md b/services/dns/Providing-Anycast-DNS.md index 7a14786..623a7df 100644 --- a/services/dns/Providing-Anycast-DNS.md +++ b/services/dns/Providing-Anycast-DNS.md @@ -10,7 +10,7 @@ Configuration requirements for all members of the anycast group are: * listen on a unicast IP too for testing/debugging reasons * with bind, please use ```minimal-responses yes;``` (goes into ```options```/```view```) -It is _really_ good to hang around in [[IRC]] to get things sorted out, if something doesn't work. Letting some people test your DNS behavior before joining the anycast-group is considered best practice - better safe than sorry. +It is _really_ good to hang around in [IRC](/IRC) to get things sorted out, if something doesn't work. Letting some people test your DNS behavior before joining the anycast-group is considered best practice - better safe than sorry. * **IP:** 172.23.0.53 * **Announciation Subnet:** 172.23.0.53/32 diff --git a/services/dns/Recursive-DNS-resolver.md b/services/dns/Recursive-DNS-resolver.md index 38b54ba..675ba64 100644 --- a/services/dns/Recursive-DNS-resolver.md +++ b/services/dns/Recursive-DNS-resolver.md @@ -1,6 +1,6 @@ If you want to run your own recursive DNS server, you must find upstream servers that are authoritative for the dn42 zones. -You may use some servers listed in the [[table of anycast servers|Providing-Anycast-DNS#Persons-providing-anycast-DNS]], or just use `172.22.119.160` and `172.22.119.163` (ns{1,2}.fritz.dn42). +You may use some servers listed in the [table of anycast servers](/Providing-Anycast-DNS#Persons-providing-anycast-DNS), or just use `172.22.119.160` and `172.22.119.163` (ns{1,2}.fritz.dn42). ## Configuration