Summary

Take control of our own DNS zones, and host them on space infra. This will be done for the following domains:

nurd.space
nurdspace.nl

Architecture

We will use two secondary nameservers. One running @ BIT/Ede, one running at Soleus/Amsterdam. On erratic, we host a hidden primary DNS server, and using wireguard tunnels, we hook these up to the secondaries. Zone updates will be sent over these wireguard links

Secondary DNS server details

services.as65342.net

ipv4: 213.154.229.26
ipv6: 2001:7b8:3:47:213:154:229:26
operator: r3boot

neutralino.soleus.nu

ipv4: 94.142.246.90
ipv6: 2a02:898:62:f6::5a
operator: BOFH team

Steps

Configure nameservers for both domains

This step has been completed

[16:36:11] alita [~] >> dig +short @213.154.229.26 soa nurd.space
ns1.r3blog.nl. hostmaster.r3blog.nl. 2023072001 86400 1800 2419200 300
[16:36:26] alita [~] >> dig +short @94.142.246.90 soa nurd.space
ns1.r3blog.nl. hostmaster.r3blog.nl. 2023072001 86400 1800 2419200 300
[16:36:33] alita [~] >> dig +short @213.154.229.26 soa nurdspace.nl
ns1.r3blog.nl. hostmaster.r3blog.nl. 2022122003 86400 1800 2419200 300
[16:36:37] alita [~] >> dig +short @94.142.246.90 soa nurdspace.nl
ns1.r3blog.nl. hostmaster.r3blog.nl. 2022122003 86400 1800 2419200 300

Request transfer keys

Done for nurd.space
nurdspace.nl waits on Network/Roadmap/WikiMigration to be completed

Request transfer of domains

Done for nurd.space

Setup primary namserver on space infrastructure

This should be a KVM, 2 cores, 1024MB ram
NSD will be used as the nameserver
Machine should be hosted on internal ip space
Wireguard tunnels need to be setup between primary and secondaries
XFR needs to be configured between primary and secondaries
Ask r3boot for a copy of the zonefiles (currently services.as65342.net is configured as a primary)