Category: News Releases

So, with Kyru coming back to our volunteer team, our projects are going through some changes. First is that Kyru is stepping up as our Project Organizer. Meaning that he will be controlling the direction that Marbled Fennec Networks is headed, what our policies are and how they are handled, as well as functioning as the chairman of Marbled Fennec Networks for the time being.

Adrian is stepping away from the chairman role and will be moving into running the Network Operations Center for FurrIX. She will no longer be on tier one support except for times when no other volunteer is able to handle tickets, instead focusing more on FurrIX for our IP transit network and services. She will still be in charge of our VRChat presence known as Remains of Avaluix, since the group is private and technically her own to manage, so that won’t change much aside from eventually reworking the digital spaces expectations.

Something that has been tabled but not yet finalized or voted on, is the possible transition from ‘marbledfennec.net’ to ‘avaluix.net’. This was tabled today and our project already holds the domain, but we need a 3/4 vote to push it through.

These changes are being done to allow our volunteers to focus on the areas that they are more familiar with and to make sure no single volunteer is wearing too many hats. This is just the start of restructuring Marbled Fennec Networks and FurrIX, as well as sorting through years of backend things that need fixing.

As you guys can see from the past few post, Kyru is returning to volunteer status as we get ready to switch back into full operation and expand our network.

He will be spending his time on tier one support and in the NOC helping us plan out and deploy our allocations across both of our servers. Also, his project is now a sister project to FurrIX as we have worked out a deal with Project Deco in exchange for his help around here.

One of the big projects involving him is reworking our terms of service, network management policy and acceptable use policy. While the spirit of these documents won’t change much, the language used in them will become cleaner.

I will be taking the time to show him around the IPAM, our routers and teaching him how to manage our name servers as time permits.

Welcome back to the team, Kyru!

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.