Homelab & Self-Hosting

Run Nextcloud, Jellyfin, Proxmox, and Docker apps on dynamic residential broadband. Free, stateless, with 60-second DNS TTL and zero commercial nagware.

Docker Compose Sidecar pfSense & OPNsense Caddy & Traefik TLS Zero Spam Confirmation

Why Self-Hosters Avoid Commercial DDNS

Self-hosting is about digital sovereignty and privacy. Yet most commercial dynamic DNS providers introduce the exact friction self-hosters try to avoid:

  • 30-Day Expiration Traps: Forcing you to click monthly verification links to keep your free hostname active.
  • Account Requirements: Linking your real email and IP history to a centralized database susceptible to credential leaks.
  • Slow TTL Caching: Setting high DNS TTLs (hours instead of seconds), meaning dropped IPs cause prolonged downtime.

XYZ.FRL operates statelessly. Hostnames have a 60-second TTL, propagate across global authoritative edge DNS servers immediately, and will never expire because there is no account database to prune.

Method 1: Docker Compose Update Sidecar

If you manage your homelab via Docker Compose, you can run a lightweight Alpine curl container directly in your stack to keep your hostname synchronized:

docker-compose.yml
services:
  ddns-updater:
    image: curlimages/curl:latest
    container_name: xyz-ddns
    restart: unless-stopped
    command: >
      sh -c '
        while true; do
          curl -fsS --user "YOUR_USERNAME:YOUR_PASSWORD" "https://xyz.frl/nic/update" || true;
          sleep 300;
        done
      '
    environment:
      - TZ=UTC
    security_opt:
      - no-new-privileges:true
    cap_drop:
      - ALL

This container consumes less than 5MB of RAM, requires no root privileges, and runs silently every 5 minutes.

Method 2: Router Integration (pfSense, OPNsense, OpenWrt)

Updating DNS directly at the perimeter router is optimal because your router detects WAN IP renegotiations instantaneously.

pfSense / OPNsense Configuration

  1. Navigate to Services → Dynamic DNS → Add.
  2. Set Service Type to Custom.
  3. Set Interface to monitor to WAN.
  4. Set Update URL to:
    https://xyz.frl/nic/update?myip=%IP%
  5. Enter your assigned username and cryptographic password into the HTTP Basic Auth fields.
  6. Save and force an update. The status indicator will turn green.

Automated TLS Certificates with Reverse Proxies

Pairing your dynamic hostname with a reverse proxy like Caddy or Traefik gives you automatic, free Let's Encrypt SSL/TLS certificates:

Caddyfile
<your-uuid>.xyz.frl {
    reverse_proxy localhost:8080
}

Caddy handles the ACME HTTP-01 challenge directly over your dynamic hostname and keeps your TLS certificate renewed without intervention.

Autonomous Homelab Agents

Using local LLM agents (like Ollama with LangGraph or Antigravity)? Homelab agents can invoke the remote MCP server to audit public DNS propagation and detect split-brain DNS resolution between your internal LAN and public WAN interfaces.

✓ Copied to clipboard!