Menu

Post image 1
Post image 2
1 / 2
0

Zero-Config DNS and Monitoring for Your Traefik Homelab

DEV Community·Luc Allaire·24 days ago
#GLddWWcQ
#traefik#docker#go#selfhosted#mesh#fullscreen
Reading 0:00
15s threshold

Every Traefik service you expose already has a Host() rule that declares its public hostname. That information exists exactly once — in a Docker label — and propagates nowhere useful. So you end up maintaining three or four systems by hand: Cloudflare for public DNS, NetBird for internal VPN-only hostnames, Uptime Kuma for monitoring — with groups, tags, and status pages configured per service. Add a container and you need to update everything manually. Remove it 4 months later and those records stay unless you remember to clean them up. traefik-mesh-companion makes the container definition the single source of truth and syncs the rest automatically. What It Does A Go sidecar that watches the Docker socket and syncs your Traefik routing labels to: NetBird — internal mesh VPN DNS records Cloudflare — A records or CNAMEs to a CF Tunnel endpoint Uptime Kuma — monitors, status page groups, tags, domain bindings Gatus (via Gatus Bridge) — endpoints and groups A single Docker Compose sidecar.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More