Category: Core

When this project first started, we borrowed a domain from Skylar’s personal domains to use for all of the routing and support gear. Somewhere around the one year mark, we were supposed to return the domain ‘fenfox.run’ back to her for use on her website. We didn’t make the original date for return and worked out a deal to keep the domain in operation for another three to four months as a stop gap measure and have finally moved everything over to ‘furrix.zone’ and seem to have no issues so far.

As of today, ‘fenfox.run’ is no longer used anywhere within MFN or FurrIX.

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.

We have been working with the LIR on setting up PTR for our ‘2602:f992:f3::/48’ network and this feature is now working correctly. Lookups will be answered by our name servers, meaning our default and member set records will now be returned. If you have a service on your subnet or a machine that needs reverse DNS name set, reach out to our support desk and let them know.