Convert all references from git.dn42.us to git.dn42.dev

The DN42 registry used to be maintained in monotone, but was moved to git following resource and performance

issues. There may still be references back to monotone in some of the documentation, but the registry location is now:

### Can I reuse my public AS number/IPv4/IPv6?

DN42 uses network addresses in the [rfc1918](https://tools.ietf.org/html/rfc1918) and [ULA](https://tools.ietf.org/html/rfc4193) ranges. These are described in detail within the sections below.

- **open** - users may request prefixes in this range, subject to any constraints that are described in the `remark` attributes

- **closed** - these ranges cannot be assigned

grep -r ^policy data/inet{,6}num/

```

`inetnum` and `inet6num` objects within the registry are used to describe the allocation of address space to users. `route` and `route6` objects in the registry are used to validate routing announcements through [ROA](https://wiki.dn42/howto/Bird#route-origin-authorization).

Globally routable prefixes are not supported in DN42; they are denied via the registry filter{6,}.txt files and many networks will filter both announcements and traffic for prefixes that are outside of the allowable ranges.

Unlike the IPv6 address space, the DN42 IPv4 space is not fully open for assignment to users; some ranges are intended for specific uses and other ranges are reserved. See the policy section, below. Users should always check the policy in the registry before requesting a prefix to be assigned.

## IPv4 Policies

The ROA table can be generated from the registry directly or you can use the following pre-built ROA tables for BIRD (generated every 30 mins from the registry):

|URL| IPv4/IPv6 |Description|

|---|---|---|

## Fill in the registry

The registry is a git repository, so objects are created by forking the main repository, making your changes and then submitting a pull request for review. See the [git documentation](https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes) and guides on [github](https://help.github.com/en/github/using-git) for how to use git to work with remote repositories.

The registry maintainers run all three scripts against each request, so please run these yourself first to check for simple errors.

*Whilst it is possible to use the web interface to edit files, you are encouraged to clone your repo locally and use the command line git tools. It's easy to do and learning how to use git is a skill worth knowing. Using the web interface creates a large number of commits and prevents you from checking your changes with the registry scripts*

To register an AS number, simply create an `aut-num` object in `data/aut-num/`.

`as-name` should be a name for your AS.

**You should allocate your AS number in the 4242420000-4242423999 range**

* [SimpleDNS](https://simpledns.com/private-ipv6)

* [Ultratools](https://www.ultratools.com/tools/rangeGenerator)

example: data/inet6num/fd35:4992:6a6d::_48

```

## Fill in the registry

The registry is a git repository, so objects are created by forking the main repository, making your changes and then submitting a pull request for review. See the [git documentation](https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes) and guides on [github](https://help.github.com/en/github/using-git) for how to use git to work with remote repositories.

The registry maintainers run all three scripts against each request, so please run these yourself first to check for simple errors.

*Whilst it is possible to use the web interface to edit files, you are encouraged to clone your repo locally and use the command line git tools. It's easy to do and learning how to use git is a skill worth knowing. Using the web interface creates a large number of commits and prevents you from checking your changes with the registry scripts*

To register an AS number, simply create an `aut-num` object in `data/aut-num/`.

`as-name` should be a name for your AS.

**You should allocate your AS number in the 4242420000-4242423999 range**

* [SimpleDNS](https://simpledns.com/private-ipv6)

* [Ultratools](https://www.ultratools.com/tools/rangeGenerator)

example: data/inet6num/fd35:4992:6a6d::_48

```

2. Convert your peer's public key to the hexadecimal DER format using the [pubkey-converter][pubkey-converter] script, if necessary.

## Configuration

### Configure the phase 1 IKE parameters

2. Convert your peer's public key to the PEM format using the [pubkey-converter][pubkey-converter] script, if necessary.

## Configuration

### Configure the phase 1 IKE parameters

Configuration of common resolver softwares to forward DNS queries for `.dn42` (and reverse DNS) IPv4 and IPv6 anycast services.

```sh

drill -D SRV _dns._udp.recursive-servers.dn42. @172.20.0.53