Hey VTs,
Skylar needs you to crawl the network and check everything connected against our documentation. The network map had errors and some of our recent task got messed up. Please take a moment to crawl the network and let her know your findings, it would be very helpful to get a few more eyes on this.
Category: Network
Post dealing with changes to how we route packets and configure our network.
We have reached a point where our name servers are working well enough for daily use that we feel like we can cut down on some of the duplicate functionality in our routing stack. At present, each router in our stack is running its own instance of Unbound for client DNS and this leads to a bunch of duplication that is probably not needed and just adds to our hypervisor’s workload.
Starting around 1000EST today, we will be turning off each router’s Unbound instance and will be updating profiles to point their DNS at our two name servers. If you are an end user or project member and you notice that DNS functions stop working, you should update your connection profiles to point their DNS at the following addresses:
- 204.12.237.197
- 173.208.212.205
- 2604:4300:f03:c1::2
- 2604:4300:a:6e::5
For our WireGuard users, this most likely means replacing the line “DNS = 2604:4300:f03:XX::1, 10.0.XX.1” with the line “DNS = 2604:4300:f03:c1::2, 2604:4300:a:6e::5” to retain DNS functions after today. We know that our DNS changes have been a moving target for our project and our users, but this should wrap things up on that front.
Around 0030EST last night, we received emails stating that the domain “marbledfennec.net” was transferred over to Porkbun after a much stressful waiting period in which our domain was not working correctly and was even offline to various parts of the web.
As of 1245EST, we have our name servers fixed including DNSSEC. Everything should be working properly now and we should be back online.