Marbled Fennec Networks

We poked the LIR a while back about our leased network range, 2602:f992:f3::/48, about getting the reverse DNS support added in and we were met with some technical issues the prevent them from delegating the zone to us.

Since then, our team has spent some time working on getting an understanding how to create and manage the reverse zone within our name servers. As of this evenin’, you can query our name servers directly to get the PTR record information for this zone from us. As configured, it probably is of little use to anyone, but the information is there and does resolve.

You can test this yourself by doing “nslookup -q=ptr 2602:f992:f3::1 multi.dns.marbledfennec.net” and you should get the result “1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.f.0.0.2.9.9.f.2.0.6.2.ip6.arpa name = icmp6.catos.furrix.zone.” back from our servers.

Our secondary server may return SERVFAIL for next 10-15 minutes as our zone updates need to transfer.
Our secondary server has transferred the zone in and is responding now.

Accounting has been finished up for the month. This post will share the details of our network usage broken down by day and which part of our projects used the network. This report does not show individual member, guest or end user usages. Only combined network usages are shown here.

Physical Network Interface:
Traffic for the physical interface shows a combined view of all project traffic, including nightly backs; games; member, guest and end user traffic and internal traffic.

Hosted Services:
Traffic for hosted services includes things such as DayZ, Minecraft and FiveM.

Name Servers:
Name server traffic includes DNS traffic that is dropped at the interface and not processed.

As mentioned in our last post, VM and VPS hosting was on the chopping block due to resources getting tighter on our physical hosts. As of today, Marbled Fennec Networks no longer offers the hosting of Virtual Machines or Virtual Private Servers for our project members or guest. We have been just barely squeaking by on disk space and have decided that for the longevity of both MFN and FurrIX, this is a service that has been cut.

Project members and guest who currently have VM or VPS service with us will continue to see their instances serviced; we won’t be accepting any new applications for this type of service and members or guest who let their service registration lapse will not be able to regain hosted services with us. We know this is not what our members and guest want to hear, but we have to keep our servers and routers operational above everything else.