Alright, not that anyone reading this or running their business this way will care, but MFN does not appreciate nor entertain cold emails about SEO, Google search ranking, social network services, domain brokering, server deployment or website optimization. Our project is currently operating with five people behind the scenes, is a very small part time ordeal and provides highly specific functionality to a very niche base of clients.
We are a zero income project. Please read this and save your fingers from the clicks to email us: we are a zero income project that operates on a month to month basis. We do not have any spare change nor the desire to spend on any third party services. Further more, those of you that do email our PR guy or our support team trying to sell your services will get your domains sent to /dev/null without recourse.
I highly do not appreciate getting emails forwarded to my inbox because someone tried messaging our support department about selling some ruckus we do not need or want.
If MFN or FurrIX ever needs a service from a third party, we will start the conversation. Not you.
Category: Operations
Information about changes or proposals that affect the way our project operates.
Hey VTs,
Skylar needs you to crawl the network and check everything connected against our documentation. The network map had errors and some of our recent task got messed up. Please take a moment to crawl the network and let her know your findings, it would be very helpful to get a few more eyes on this.
We have reached a point where our name servers are working well enough for daily use that we feel like we can cut down on some of the duplicate functionality in our routing stack. At present, each router in our stack is running its own instance of Unbound for client DNS and this leads to a bunch of duplication that is probably not needed and just adds to our hypervisor’s workload.
Starting around 1000EST today, we will be turning off each router’s Unbound instance and will be updating profiles to point their DNS at our two name servers. If you are an end user or project member and you notice that DNS functions stop working, you should update your connection profiles to point their DNS at the following addresses:
- 204.12.237.197
- 173.208.212.205
- 2604:4300:f03:c1::2
- 2604:4300:a:6e::5
For our WireGuard users, this most likely means replacing the line “DNS = 2604:4300:f03:XX::1, 10.0.XX.1” with the line “DNS = 2604:4300:f03:c1::2, 2604:4300:a:6e::5” to retain DNS functions after today. We know that our DNS changes have been a moving target for our project and our users, but this should wrap things up on that front.