Category: Network

Post dealing with changes to how we route packets and configure our network.

Name Server Changes

Due to people not reading the related DNS entries before listing our servers on their websites or setting up their services to use our name servers, there have been some changes to our network setup. Make sure to re-read the details below and update any listings or software that you have attached to our name servers.

The main change is that ‘dns.marbledfennec.net’ now points to all of our name servers and the subdomain ‘dns2.marbledfennec.net’ no longer exist.

For a short period of time, ‘multi.dns.marbledfennec.net’ will continue to exist but it is set to be removed from the network by the end of January, 2025.

[Advisory] WireGuard on Windows 11

If you are on Windows 11 and are using WireGuard to connect to our network for v4 access, you may need to change your address from x.x.x.x/32 to either x.x.x.x/28 or x.x.x.x/29 depending on which subnet size our volunteer techs setup for your use.

This appears to only be affecting Windows 11 machines where using a /32 causes the platform to fail to route traffic correctly. This is a new issue that we have been recently dealing with and this appears to be the fix. Oddly, using a /128 on the IPv6 does not cause this same issue. This is only affecting this platform and does not seem to affect Linux or Android.

We are aware of issues with the secondary host!

We are aware of some ongoing issues with the network that services our secondary host which runs our status page and slave name server. The data center has been contacted and has let us know that they are having internal issues and are working to resolve it. During this time secondary services might become unusable off and on.


Additionally, our volunteers are working off and on on some updates and changes to the hypervisor on the secondary. Expect some minor outages today caused by our team.