Category: News Releases

Our team has moved all but our v6 edge router over to using one of our DNS servers at
dns.fenfox.run and as far as we can tell, everything is running as it should and the move was
transparent without any hiccups. The means all of our project members and end users will
now have access to both ICANN and OpenNIC domains.

Marbled Fennec Networks is currently working on testing out our own pair of DNS servers
for servicing the network. So far things look like they are running well and response times are fair.
If the testing continues to work as expected, we are considering switching all routers over to using
the servers “dns.fenfox.run” and “dns2.fenfox.run” as their upstream DNS.

These changes, if they happen (won’t know for another few hours), should be completely transparent
to our project members and end users.

Our team managed to get three server and two routers updated today, so some of the work log has been cleared. Still have three routers to update and a handful of VPS instances.

Side note, due to issues outside of MFN’s control, our project manager has left the project. Starting tomorrow, the PM position will be open for members and VTs to apply for, if they wish to take a go at running the project. If interested, get in contact with Skylar.

After a handful of years of our project using the very easy and simple to manage FlatPress platform, we are moving to a newer platform. Currently we are looking into WordPress for our website needs and have begun the migration.

During this time, both versions of our website will be kept in step with one another for up to 45 days, after which the old website will be retired from the network.

The new website can be reached at https://www.marbledfennec.net as usual and the old version of the website can be found at https://old.marbledfennec.net/

UPDATE Two:
Combing through the physical host logs and reading things line by
line turns out a set of errors that might be concerning to our
operations, but we aren’t sure just yet.

Apr 25 12:04:34 adrian kernel: mce: [Hardware Error]: Machine check events logged
Apr 25 12:04:34 adrian kernel: microcode: CPU12: patch_level=0x08701021
Apr 25 12:04:34 adrian kernel: microcode: CPU13: patch_level=0x08701021
Apr 25 12:04:34 adrian kernel: microcode: CPU14: patch_level=0x08701021
Apr 25 12:04:34 adrian kernel: microcode: CPU15: patch_level=0x08701021
Apr 25 12:04:34 adrian kernel: mce: [Hardware Error]: CPU 12: Machine Check: 0 Bank 5: bea0000000000108
Apr 25 12:04:34 adrian kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffffa5e675c2 MISC d012000100000000 SYND 4d000000 IPID 500b000000000 
Apr 25 12:04:34 adrian kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1714061070 SOCKET 0 APIC 9 microcode 8701021
Apr 25 12:04:34 adrian kernel: microcode: CPU0: patch_level=0x08701021

We are continuing to check on the machine and watching for problems
that may be affecting us.

UPDATE One:
We got in touch with the data center and they are saying
“As these are unmanaged servers, we do not actively monitor
customer services, so we do not know when or why a services
goes offline.” Which we understand, the operation of the
hardware is on us, but this is something outside of our
project from the looks of it.

Our team will continue to work on restoring network services
and will monitor the system for the next few hours to see
if any issues arise.

—

We got some alarms sent to our team around 1214EST this
afternoon that large portions of our network went offline
without warning. Upon logging into our management consoles
and looking things over, it seems that our physical host
“Adrian” rebooted.

We have reached out to the data center to see what may have
happened and our team is in the process of restoring our
network functionality.