A ZimaBoard 2 NAS with DNS Redundancy and a Documented Homelab

Eva Wong is the Technical Writer and resident tinkerer at ZimaSpace. A lifelong geek with a passion for homelabs and open-source software, she specializes in translating complex technical concepts into accessible, hands-on guides. Eva believes that self-hosting should be fun, not intimidating. Through her tutorials, she empowers the community to demystify hardware setups, from building their first NAS to mastering Docker containers.

Thank you to u/benhaube for sharing a homelab built around useful network services and the documentation that keeps them manageable. A ZimaBoard 2 1664-based NAS now sits alongside two Raspberry Pis, with DNS, remote access, printing and a written record of the environment shaping the story.

The Self-Hosting Day contribution begins with a Raspberry Pi 4B in 2020–21 and follows the installation into a ten-inch mini rack. The distinctive part is the creator’s approach to maintenance: configuration should be documented so that it does not have to live entirely in memory.

A Raspberry Pi Started with Three Everyday Jobs

The first machine was a Pi 4B with 4 GB of RAM and a 64 GB microSD card. Its planned jobs were straightforward: Pi-hole to reduce ads and tracking, WireGuard for remote access, and an IPP server for a Brother laser printer that connected only through USB.

Those services gave the small computer a place in the household. Network filtering, reaching home while away, and using an existing printer were concrete reasons to learn the tools. Each task connected the hardware to something that was already useful.

The original Pi remained in the lab as the collection grew. A second Pi joined it, followed by a NAS built around a ZimaBoard 2 1664. The contribution describes adding responsibilities to an existing installation rather than replacing the whole environment with one new machine.

That gradual expansion resembles u/2Hard4Him’s move from Pi-hole to a family server. The details differ, but both accounts begin with a manageable service that makes the next step worth exploring.

The ZimaBoard 2 NAS Has a Place in a Larger Network

The NAS is mounted in a ten-inch mini rack with a 3D-printed bracket. The same rack includes the modem and a UGREEN UM106X switch. The original photograph shows the physical arrangement, including printed panels, cabling and the network equipment below the server.

benhaube’s ten-inch mini rack with a ZimaBoard 2 NAS, printed mounts and network equipment
The contributor’s original ten-inch rack photograph, with printed mounts, the NAS and network equipment. The UGREEN switch is part of the reported setup. Source: u/benhaube.

The wider home network uses an Asus RT-BE92U main router, an RT-AX55 mesh node and three Ethernet switches. The contributor reports running Asuswrt-Merlin on the main router and values its scripting and firewall capabilities.

The two Pi servers connect through the upstairs mesh node, while the NAS and modem occupy the rack. That gives the installation a physical geography as well as a service list: the machines live in different places, with a network path between them.

Component or service Role described in the account Relevant detail
Original Raspberry Pi 4B Starting point for household network services Pi-hole, WireGuard and USB-printer sharing were the initial goals
Two Raspberry Pi servers Part of the expanded lab Connected through the upstairs mesh node
ZimaBoard 2 1664 NAS Storage host and documentation web-server host Mounted in the ten-inch rack with a printed bracket
Technitium DNS DNS service replacing the earlier Pi-hole setup The creator reports a cluster for high availability
Material for MkDocs and Nginx Written lab documentation presented as a static website Hosted on the NAS and made reachable through a Cloudflare tunnel

DNS Evolved from Ad Blocking to a Clustered Service

The author moved from Pi-hole to Technitium and describes running it in a high-availability cluster. DNS had become an area to develop further as the rest of the environment expanded.

The official Technitium DNS Server project explains its DNS and filtering capabilities. The Reddit account establishes that the creator uses it in a clustered arrangement, but does not describe the exact node layout, synchronization settings or client behavior during a failure.

That leaves a useful boundary around the story. The architectural intent is redundancy for a service the household relies on. There is no published failover benchmark from which to promise a particular recovery time or an interruption-free result in another network.

The original Pi-hole project still matters to the narrative because it provided the entry point. The later DNS arrangement shows how one familiar task can become a deeper area of learning once a creator has an environment to maintain.

Markdown Documentation Became Part of the Infrastructure

The contributor works in IT and connects that experience to the importance of recording how systems are configured. As the home lab changed, they created thorough documentation in Markdown using Material for MkDocs.

The generated static website runs in an Nginx container on the NAS. A Cloudflare tunnel makes it reachable over the internet. The contribution describes the publishing path, but does not provide the site’s access policy or reproduce its contents.

The Material for MkDocs documentation provides the reference for the tool used in that workflow. In this installation, the resulting website serves as a record of the creator’s own decisions.

The benefit the author emphasizes is practical: they do not have to remember every configuration detail. Written information can help them understand the environment again when something fails or when an earlier choice needs to be revisited.

This connects with u/jc-21’s account of maintaining a deliberately small homelab. Both contributors value understanding what they run. Here, a dedicated documentation site is part of how that understanding is retained.

The Network Connections Are Specific, but the Performance Is Unmeasured

The creator uses the switch’s 10 Gb SFP+ port with an Ethernet transceiver as an uplink and reports using both 2.5 GbE ports on the ZimaBoard 2. Those details explain the attention given to the path between the rack and the wider network.

The source does not identify a bonding mode, a link-aggregation configuration or an individual file-transfer result. Using two network interfaces should therefore remain a description of the installation, rather than being converted into a claim that every connection automatically receives their combined bandwidth.

The same care applies to recovery. The creator sees documentation as a way to restore service more quickly, but the contribution does not include a timed rebuild or a full disaster-recovery exercise. The documented habit is valuable in its own right without adding an unreported test result.

Readers interested in another physically compact build can compare the silent dual-NVMe ZimaBoard 2 homelab. Its custom enclosure addresses a different need, while this rack emphasizes connections, shared services and maintainability.

FAQ

Which Zima device is part of this lab?

The contributor identifies a ZimaBoard 2 1664-based NAS. It sits alongside the original Raspberry Pi and a second Pi, rather than replacing every machine in the installation.

What operating system runs on the NAS?

The Reddit contribution does not name the NAS operating system. It establishes the ZimaBoard 2 hardware and an Nginx container used to host the documentation site.

Is Pi-hole still the reported DNS system?

The early project used Pi-hole. The author later moved to Technitium and describes clustering that service for high availability.

Do the two 2.5 GbE ports prove a doubled transfer speed?

No transfer measurement or bonding arrangement is supplied. The source says both ports are used; it does not establish the throughput of a particular application or connection.

Does the public account provide the documentation or recovery procedure?

It names Markdown, Material for MkDocs, Nginx and Cloudflare Tunnel. It does not include the documentation contents, credentials, access rules or a complete restore procedure.

Conclusion

benhaube’s lab grew from three everyday Raspberry Pi tasks into a ZimaBoard 2 NAS, clustered DNS and a network spread across the home. The equipment gives the services a physical home, while documentation gives the configuration a durable record.

The lasting idea is simple: maintaining a homelab includes preserving the knowledge needed to understand it. In this story, writing things down is as much a part of the setup as the printed mounts and network cables.

Welcome to the ZimaSpace community! Share your setup, ask questions, and explore practical build guides, real user stories, and product updates with fellow self-hosters.

Zima Campaign Hub

More to Read

Get More Builds Like This

Stay in the Loop

Get updates from Zima - new products, exclusive deals, and real builds from the community.

Stay in the Loop preferences

We respect your inbox. Unsubscribe anytime.