Replace wikilink style links with generic markdown

### How do I connect to DN42?

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.

## Why dn42?

## Join or Contact us

## External resources about dn42

<div class='toc-title'>Site Links</div>

* How-To

* Services

* Internal

* External Tools

--------------

Members of the dn42 network mostly communicate via IRC or the mailing list.

## Mailing list

Channel #dn42 in [hackint](http://www.hackint.eu/)

## Twitter

## First Steps

3. Get the following details:

* Tunnel configuration (OpenVPN, IPsec, QuickTun)

* AS numbers

* Basic EdgeOS knowledge is required

3) You need following data from the peer

## DNS

## What is ROA?

## CA

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

* 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.)_

### Tor

### Telegram

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

### Split horizon DNS

In this configuration, you run your own, caching resolver but forward DN42 related queries (with recursion bit set)

### Full recursion

Authoritative DNS for DN42 is provided by the *.delegation-servers.dn42 servers, see the DNS architecture here

## Further Information

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.

## Prerequisites

* 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

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.

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

* Choose the implementation(s) you want to use. It should support at least AXFR+NOTIFY (*.delegation-servers.dn42) or DNSSEC (*.recursive-servers.dn42).

* 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:

# See also

***

# Original DNS (deprecated)

***

*(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`.

## Using the DNS service

### Forwarding `.dn42` queries to the anycast resolver

### Recursive resolver

### Building the dn42 zones from the registry

## Register a `.dn42` domain name

## DNS services for other networks

## Providing DNS services

This is a new effort to build a DNS system that mirrors how DNS was designed to work in clearnet.

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.

## Peering with the collector

## DNS zones

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).

# Software

* [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

## Configuration

* listen on a unicast IP too for testing/debugging reasons

* with bind, please use ```minimal-responses yes;``` (goes into ```options```/```view```)

* **IP:** 172.23.0.53

* **Announciation Subnet:** 172.23.0.53/32

If you want to run your own recursive DNS server, you must find upstream servers that are authoritative for the dn42 zones.

## Configuration