Thursday, May 14, 2026
[Transparency Report #005][OPERATIONS] Name servers moved into FurrIX
What are Transparency Reports?
As a community operated and governed virtual internet exchange, FurrIX has
to maintain and foster open and honest communication with our exchange
members. This means that from time to time, there will be items that come
up during our operations that could or do affect the exchange and our team
will publish notices in order to keep everyone in the know. As a community
internet exchange hobby project, FurrIX aims to have fully open communication
where practical.
What Happened?
FurrIX has completed the planned transition of its hybrid name servers from
MFN’s legacy network and DNS zone into full FurrIX operational control. This fulfills
the February 2026 agreement between MFN and FurrIX to migrate DNS operations while
maintaining continuity for all members. The move consolidates name server governance,
improves operational clarity and aligns DNS identity with the rest of the FurrIX
infrastructure.
We consulted with the operator of the newly scoped MFN project and mutually agreed to
leave their zone and glue records unchanged at the registry for now. Operationally, however,
FurrIX.zone no longer relies on NS entries from the MFN zone and the MFN operator is now
free to manage their DNS zone independently without requiring support from the FurrIX team.
Why this rework is needed:
With FurrIX taking over the network components previously operated under MFN, several
updates were required to maintain a clean governance boundary and preserve FurrIX’s
independent project status:
- Name server identity:
NS1 and NS2 now operate solely under the FurrIX namespace, retiring the hybrid MFN/FurrIX
state used during the transition period. (MFN’s NS entries remain available for their own use.)
- Operational ownership:
FurrIX now maintains full control of NS configuration, monitoring and security posture
completing the handoff from MFN and allowing the vIX to manage these servers as needed
- NS Records:
FurrIX NS glue records have been updated.
What this means for members of the exchange:
- No member impact —
This is a backend operational change and members should not experience any
difference in network behavior.
Are exchange operations affected?
Functionally, nothing member facing has changed.