Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/IsaiasCarrion/Homelab/llms.txt

Use this file to discover all available pages before exploring further.

The homelab network is built on a single flat 192.168.1.0/24 subnet, with a deliberately structured IP reservation scheme that makes it easy to identify a device’s role at a glance. Rather than relying on DHCP for infrastructure hosts, all servers, hypervisors, containers, and VMs are assigned static IPs within reserved ranges. Client devices and temporary machines fall into the DHCP pool at the upper end of the subnet. Internal DNS resolution is handled by a self-hosted Technitium DNS server, exposing all services under the home.arpa local domain.

​
Network Configuration

SettingValue
Network192.168.1.0/24
Gateway192.168.1.1
DNS Primary192.168.1.21
Local Domainhome.arpa
DHCP Range192.168.1.100–254

​
IP Reservation Scheme

The address space is divided into logical blocks, each dedicated to a specific class of device. This makes it straightforward to read a device’s IP and immediately understand its function within the homelab.
RangeUse
192.168.1.1Router
192.168.1.2–19Infrastructure
192.168.1.20–29Hypervisors
192.168.1.30–39Docker / Dev
192.168.1.40–49Storage
192.168.1.50–69Labs / AI
192.168.1.70–99Expansion
192.168.1.100–254DHCP (clients)
The structured IP scheme makes it easy to identify a device’s role by its IP address alone. A host at 192.168.1.22 is immediately recognisable as a hypervisor-range guest, while one at 192.168.1.55 belongs to the Labs / AI block — no lookup needed.

​
Internal DNS

All homelab services are resolvable by hostname within the home.arpa local domain. This is powered by a Technitium DNS server running in an LXC container at 192.168.1.21 (dns.home.arpa). Technitium DNS serves the following roles:
  • Authoritative DNS for the home.arpa zone, resolving internal hostnames to their static IPs
  • DNS cache to reduce upstream query latency for client devices
  • Split DNS so that internal service names never leak to public resolvers
  • Ad and tracker blocking via a curated blocklist (big.oisd.nl), with blocked domains returning NXDOMAIN
  • Wildcard records to simplify adding new subdomains under home.arpa
All infrastructure hosts and LXC containers are configured to use 192.168.1.21 as their primary DNS resolver, so hostnames like portainer.home.arpa or npm.home.arpa resolve correctly from anywhere on the network.

​
Useful Network Commands

The following commands are helpful for quickly auditing the network, checking interface configuration, or verifying routing from any Linux host on the homelab. 
# Discover all active hosts on the subnet
nmap -sn 192.168.1.0/24

# Display network interface addresses and status
ip a

# Display the routing table
ip route

Build docs developers (and LLMs) love

Get started for freeTalk to us