Files
MajorWiki/02-selfhosting/dns-networking/network-overview.md
MajorLinux 87d63039af wiki: audit fixes — broken links, wikilinks, frontmatter, stale content (66 files)
- Fixed 4 broken markdown links (bad relative paths in See Also sections)
- Corrected n8n port binding to 127.0.0.1:5678 (matches actual deployment)
- Updated SnapRAID article with actual majorhome paths (/majorRAID, disk1-3)
- Converted 67 Obsidian wikilinks to relative markdown links or plain text
- Added YAML frontmatter to 35 articles missing it entirely
- Completed frontmatter on 8 articles with missing fields

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-02 11:16:29 -04:00

1.4 KiB

title, domain, category, tags, status, created, updated
title domain category tags status created updated
Network Overview selfhosting dns-networking
tailscale
networking
infrastructure
dns
vpn
published 2026-04-02 2026-04-02

🌐 Network Overview

The MajorsHouse infrastructure is connected via a private Tailscale mesh network. This allows secure, peer-to-peer communication between devices across different geographic locations (US and UK) without exposing services to the public internet.

🏛️ Infrastructure Summary

  • Address Space: 100.x.x.x (Tailscale CGNAT)
  • Management: Centralized via Ansible (MajorAnsible repo)
  • Host Groupings: Functional (web, mail, homelab, bots), OS (Fedora, Ubuntu), and Location (US, UK).

🌍 Geographic Nodes

Host Location IP OS
dcaprod 🇺🇸 US 100.104.11.146 Ubuntu 24.04
majortoot 🇺🇸 US 100.110.197.17 Ubuntu 24.04
majorhome 🇺🇸 US 100.120.209.106 Fedora 43
teelia 🇬🇧 UK 100.120.32.69 Ubuntu 24.04

🔗 Tailscale Setup

Tailscale is configured as a persistent service on all nodes. Key features used include:

  • Tailscale SSH: Enabled for secure management via Ansible.
  • MagicDNS: Used for internal hostname resolution (e.g., majorlab.tailscale.net).
  • ACLs: Managed via the Tailscale admin console to restrict cross-group communication where necessary.

Last updated: 2026-03-04