Saturday, March 28, 2026
Ongoing Name Server Attacks
FurrIX is seeing attacks on our name servers that have not let
up for a few hours now and as a result we have had to tighten
our rate limits and start dropping excessive traffic.
The way things are going, we will not be letting up on our rate
limits any time soon.
If you are being affected by these changes, you can send an
email off to ‘nameservers at marbledfennec dot net’ and request
a whitelisting that will bypass the limits. We will require knowing
you use case, however.
Friday, March 27, 2026
Huh…Neat.
This is not a network/project related post, but occasionally
we’ll do a search to where all our domain pops up and who
knows about our existence-
Turns out another fur on FA found us and has our website
under their favorites, that’s kind of neat! Just something
I thought was cool, and who knows, maybe one day they’ll
see this post.
Wednesday, March 25, 2026
Agreement Reached with MFN
We’ve been working on our agreement with Marbled Fennec Networks
in the background and have reached what we deem to be an acceptable
way of moving forward and ensuring the survival of both projects, as
well as allowing us both to do our own thing on the same hardware.
This new version is what is being used to govern interactions and
responsibilities between both of our projects as of March 25th, 2026.
You can review the agreement at:
This page…
[Name Servers] Updated Configuration
We have been seeing a lot of DNS amplification attacks ongoing
during the past few weeks and have adjusted our name server
configuration to start rate-limiting and dropping request a fair
bit sooner.
We have also changed the graphs that we are showing for
the server status page.
Tuesday, March 24, 2026
[Incident Report #031][NET] Connectivity Issues with 2602:F992:EC::/46
Update:
Appears our static route did not get migrated to the new hardware
at the data center. This has been resolved and our services should
be back online momentarily!
What Happened?
Our upstream provider performed some upkeep on the data center on
Mar 20th and since then our routed subnet has not be working properly.
We are looking into this as it affect our IPAM, NMS, PBS and a few other
services that assist us with managing our network.
This is also affects our secondary name server, as it currently does not
have IPv6 service.
We are seeing the following issues:
- No IPv6 connectivity for NS2, affecting private and public resolution request
- No PBS backups for either MFN, FurrIX or Maows.Gay
- No NMS accounting or error tracking
- No status graphs on our website are updating
What are we doing to work on this?
- We have performed internal and external networking checks
- We have reached out to our upstream provider with our findings
At the moment, we will have to wait to hear back from the data center.