mirror of
https://git.dn42.dev/wiki/wiki
synced 2025-03-12 18:56:33 +00:00
update "git.dn42.us" links
This commit is contained in:
parent
a9a1afe795
commit
7d5913c20d
@ -31,7 +31,7 @@ Keep in mind that certificates are just public keys wrapped with some extra meta
|
||||
### Conversion tool
|
||||
Different implementations use different formats to represent public keys, and it's necessary to be able to convert between them. Here is a script for that purpose:
|
||||
|
||||
https://git.dn42.us/ryan/pubkey-converter/raw/master/pubkey-converter.pl
|
||||
[https://raw.githubusercontent.com/zeroae/pubkey-converter/master/pubkey-converter.pl](https://raw.githubusercontent.com/zeroae/pubkey-converter/master/pubkey-converter.pl)
|
||||
|
||||
### How-To examples
|
||||
| Implementation | Key format |
|
||||
|
@ -22,23 +22,23 @@ It provides the router with validity information regarding prefix origination:
|
||||
## How can I implement ROA on dn42?
|
||||
|
||||
On dn42 we generate ROA information from the dn42 registry.
|
||||
ROA json/bird files can be generated using [dn42regsrv](https://git.dn42.us/burble/dn42regsrv).
|
||||
ROA json/bird files can be generated using [dn42regsrv](https://git.burble.com/burble.dn42/dn42regsrv).
|
||||
It is also possible to integrate this with a RTR cache server such as [gortr](https://github.com/cloudflare/gortr).
|
||||
|
||||
### dn42regsrv
|
||||
|
||||
You can find a hosted example of dn42regsrv at https://explorer.burble.com/
|
||||
|
||||
Instructions on how to host dn42regsrv yourself can be found on the git repo of [dn42regsrv](https://git.dn42.us/burble/dn42regsrv).
|
||||
Instructions on how to host dn42regsrv yourself can be found on the git repo of [dn42regsrv](https://git.burble.com/burble.dn42/dn42regsrv).
|
||||
|
||||
You can also run dn42regsrv via docker (then available at 127.0.0.1:8042):
|
||||
|
||||
git checkout https://git.dn42.us/burble/dn42regsrv.git .
|
||||
git checkout https://git.burble.com/burble.dn42/dn42regsrv.git .
|
||||
cd contrib/docker
|
||||
./build.sh
|
||||
docker-compose up -d
|
||||
|
||||
Documentation for the api endpoints can be found here: https://git.dn42.us/burble/dn42regsrv/src/master/API.md
|
||||
Documentation for the api endpoints can be found here: https://git.burble.com/burble.dn42/dn42regsrv/src/master/API.md
|
||||
|
||||
### gortr
|
||||
|
||||
|
@ -7,7 +7,7 @@ To use the service, please message Kioubit on IRC to have your domain activated
|
||||
|
||||
## Registry REST API
|
||||
|
||||
[dn42regsrv](https://git.dn42.us/burble/dn42regsrv) is a REST API for the DN42 registry that provides a bridge between interactive applications and the registry.
|
||||
[dn42regsrv](https://git.burble.com/burble.dn42/dn42regsrv) is a REST API for the DN42 registry that provides a bridge between interactive applications and the registry.
|
||||
|
||||
As well as the main REST API to the DN42 registry, the server can also generate ROA tables and provides a small web application for exploring registry data.
|
||||
|
||||
|
@ -6,7 +6,7 @@ After frequent issues with the [Old Hierarchical DNS](Old-Hierarchical-DNS) syst
|
||||
# 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).
|
||||
|
||||
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.
|
||||
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.dev/dn42/registry/src/master/data/dns/recursive-servers.dn42). Please make sure you fully understand the consequences and fully trust these operators.
|
||||
|
||||
You can also use the globally anycasted a.recursive-servers.dn42 but you won't have any control over which instance you get. This is a **very bad idea** from a security standpoint.
|
||||
|
||||
|
@ -53,7 +53,7 @@ Privacy mode is enabled, please call the bot with @DN42WhoisBot when necessary.
|
||||
|
||||
[https://explorer.burble.dn42/](https://explorer.burble.dn42/) ([https://explorer.burble.com/](https://explorer.burble.com/) via clearnet) provides a web interface and REST API for querying the DN42 registry.
|
||||
|
||||
The service is provided by [dn42regsrv](https://git.dn42.us/burble/dn42regsrv) which can also be run locally.
|
||||
The service is provided by [dn42regsrv](https://git.burble.com/burble.dn42/dn42regsrv) which can also be run locally.
|
||||
|
||||
## Authentication
|
||||
|
||||
@ -76,7 +76,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).
|
||||
* [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.
|
||||
* [whois42d](https://git.dn42.dev/registry/whois42d) written in golang, lightweight/fast, whois server with support for all registry objects, type filtering and systemd socket activation.
|
||||
|
||||
# Whois daemons
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user