Changes in 7d5913c: update "git.dn42.us" links

				howto/IPsec-with-PublicKeys.md
			
          @@ -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      |

				howto/ROA-slash-RPKI.md
			
          @@ -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

				internal/APIs.md
			
          @@ -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.

				services/New-DNS.md
			
          @@ -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.

				services/Whois.md
			
          @@ -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

...	...	@@ -31,7 +31,7 @@ Keep in mind that certificates are just public keys wrapped with some extra meta
31	31	### Conversion tool
32	32	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:
33	33
34		-https://git.dn42.us/ryan/pubkey-converter/raw/master/pubkey-converter.pl
	34	+[https://raw.githubusercontent.com/zeroae/pubkey-converter/master/pubkey-converter.pl](https://raw.githubusercontent.com/zeroae/pubkey-converter/master/pubkey-converter.pl)
35	35
36	36	### How-To examples
37	37	\| Implementation \| Key format \|

...	...	@@ -22,23 +22,23 @@ It provides the router with validity information regarding prefix origination:
22	22	## How can I implement ROA on dn42?
23	23
24	24	On dn42 we generate ROA information from the dn42 registry.
25		-ROA json/bird files can be generated using [dn42regsrv](https://git.dn42.us/burble/dn42regsrv).
	25	+ROA json/bird files can be generated using [dn42regsrv](https://git.burble.com/burble.dn42/dn42regsrv).
26	26	It is also possible to integrate this with a RTR cache server such as [gortr](https://github.com/cloudflare/gortr).
27	27
28	28	### dn42regsrv
29	29
30	30	You can find a hosted example of dn42regsrv at https://explorer.burble.com/
31	31
32		-Instructions on how to host dn42regsrv yourself can be found on the git repo of [dn42regsrv](https://git.dn42.us/burble/dn42regsrv).
	32	+Instructions on how to host dn42regsrv yourself can be found on the git repo of [dn42regsrv](https://git.burble.com/burble.dn42/dn42regsrv).
33	33
34	34	You can also run dn42regsrv via docker (then available at 127.0.0.1:8042):
35	35
36		- git checkout https://git.dn42.us/burble/dn42regsrv.git .
	36	+ git checkout https://git.burble.com/burble.dn42/dn42regsrv.git .
37	37	cd contrib/docker
38	38	./build.sh
39	39	docker-compose up -d
40	40
41		-Documentation for the api endpoints can be found here: https://git.dn42.us/burble/dn42regsrv/src/master/API.md
	41	+Documentation for the api endpoints can be found here: https://git.burble.com/burble.dn42/dn42regsrv/src/master/API.md
42	42
43	43	### gortr
44	44

...	...	@@ -53,7 +53,7 @@ Privacy mode is enabled, please call the bot with @DN42WhoisBot when necessary.
53	53
54	54	[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.
55	55
56		-The service is provided by [dn42regsrv](https://git.dn42.us/burble/dn42regsrv) which can also be run locally.
	56	+The service is provided by [dn42regsrv](https://git.burble.com/burble.dn42/dn42regsrv) which can also be run locally.
57	57
58	58	## Authentication
59	59
...	...	@@ -76,7 +76,7 @@ The idea comes from the guys at cymru.com, who provide this service for the Inte
76	76	# Software
77	77
78	78	* [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).
79		- * [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.
	79	+ * [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.
80	80
81	81	# Whois daemons
82	82

...	...	@@ -7,7 +7,7 @@ To use the service, please message Kioubit on IRC to have your domain activated
7	7
8	8	## Registry REST API
9	9
10		-[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.
	10	+[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.
11	11
12	12	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.
13	13

...	...	@@ -6,7 +6,7 @@ After frequent issues with the [Old Hierarchical DNS](Old-Hierarchical-DNS) syst
6	6	# End Users
7	7	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).
8	8
9		-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.
	9	+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.
10	10
11	11	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.
12	12