Category: News Releases

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.

Reached out to our data center about pointing the reverse zone for our main /48 to our name servers and they approved it. As of today, we are in control of the reverse zone meaning that we can now set records for our project members and end users.

We have also changed the way we set records for our members and users:

• For all members, when you are given access to a subnet from our project, your subnet will receive a PTR record on the ::0 address in the format <subnet-id>.<member-nickname>.<city>.<state/province>.<country>.<router>.furrix.zone. For example: ‘sub40-64.foxxo.jacksv.fl.us.ikus.furrix.zone’ would show that you have access to the subnet ‘2604:4300:f03:40::/64’ and you are based out Jacksonville, Florida.
• For our members who are sharing their access with another member, the suffix for PTR records will always be <device>.<shared-to-nickname>.<shared-from-nickname>.<city>.<state/province>.<country>.<router>.furrix.zone. For example: ‘slate.smol-dwagon.ty-dwagon.longv.tx.us.catos.furrix.zone’ would show that you are allowing another member to make use of your subnet, possibly for in network routing.
• Members are allowed to supply our network engineers with their own PTR prefixes, given that the chosen prefix makes sense and is not derogatory or otherwise. Device names, floor locations, etc are permitted. Be aware that PTR records are globally viewable.

A better example of the use of PTR records within our project is the record for ‘2604:4300:f03::’ which returns the following data: ’30f.0034.4062.kc.mo.us.furrix.zone’ – ’30f.0034.4062′ is our IPv6 prefix entered backwards which identifies our network. – ‘kc.mo.us’ stands for Kansas City, MO, US which identifies where our network core is operated out of – ‘furrix.zone’ identifies our project as the network operator.

As you can see, having support for this is a massive help to our volunteers when needing to check who is responsible for traffic on our network or for when project members or end users have a protocol or software stack that requires a record is set in order to function properly.

Marbled Fennec Networks has gone through the interview process, vetting and getting to know a new volunteer who has passed all of our checks and is being setup to work alongside our teams. Aurora is a Florida fur who will be going through training with our network volunteers to begin their role as the secondary tech for our networking stack. Once everything is in place for them, they will be responsible for things like firmware upgrades, managing a Minecraft instance and helping with the support desk.