Home Network Architecture Standard¶

v1.1 | Build 002.20260815.014302Z

Architecture standard for the McGuckin.Net home network.

McGuckin Home Network

Network Architecture Standard

Version 0.2 | August 14, 2026

1. Network Metadata¶

2. Scope¶

This document defines the canonical hostname, IP addressing, DNS naming, and infrastructure classification standards for the McGuckin Home Network. It serves as the authoritative reference for assigning network identities to infrastructure devices and services.

Operational procedures, maintenance tasks, firmware management, backup procedures, and configuration instructions are documented separately.

In the event of any discrepancy between system configuration, personal notes, or other documentation, this document is the authoritative reference for infrastructure hostnames, static IPv4 assignments, and service DNS names.

This document intentionally excludes operational procedures, implementation guidance, and platform-specific configuration, which are documented in separate standards.

3. Design Philosophy¶

3.1 Infrastructure Philosophy¶

• Infrastructure devices receive static IP addresses.

• Client devices remain in the DHCP pool unless a specific operational requirement exists.

• Infrastructure is classified by its primary network role, not by every secondary capability a device provides.

3.2 Naming Philosophy¶

• Hostnames identify devices.

• DNS names identify services.

• IP ranges identify a device's primary role.

• Hardware may be replaced without requiring hostname or service DNS changes.

3.3 Hostname Standards¶

• Use lowercase letters.

• Separate words with hyphens.

• Prefer functional or location-based names.

• Do not include vendor or model names.

• Keep hostnames stable across hardware replacements whenever practical.

• Italicized entries identify future projects.

4. IP Address Allocation Policy¶

Note: Reserved address ranges should not be assigned to general-purpose client devices.

5. Infrastructure Inventory¶

All listed devices use static IPv4 addresses. Reserved rows preserve capacity within each functional range. Devices not listed in this section are expected to receive addresses from the DHCP client pool unless an operational requirement dictates otherwise.

5.1 Core Infrastructure¶

5.2 Servers¶

5.3 Automation Infrastructure¶

5.4 Media Infrastructure¶

5.5 Security¶

5.6 Office & Communications¶

5.7 Storage¶

5.8 Research, Development & Testing¶

5.9 Future Infrastructure¶

5.10 Out-of-Band (OOB) Management¶

Appendix A - Service DNS Directory¶

Appendix B - Retired Devices¶

Appendix C - Revision History¶

Document Control¶