---
title: "Discussion on \"Zero-Config DNS and Monitoring for Your Traefik Homelab\" | Hashnode"
description: "Discussion on \"Zero-Config DNS and Monitoring for Your Traefik Homelab\". Self-hosted infrastructure and DevOps tooling."
url: "https://hashnode.com/posts/zero-config-dns-and-monitoring-for-your-traefik-homelab/69fe7b02f239332df42533cf"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Zero-Config DNS and Monitoring for Your Traefik Homelab](https://blog.wolf-361.ca/zero-config-dns-and-monitoring-for-your-traefik-homelab?utm_source=hashnode&utm_medium=feed)

Self-hosted infrastructure and DevOps tooling.

May 9 · 4 min read · blog.wolf-361.ca  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#docker](https://hashnode.com/tag/docker)
-   [#selfhosted](https://hashnode.com/tag/selfhosted)
-   [#go](https://hashnode.com/tag/go)
-   [#traefik](https://hashnode.com/tag/traefik)
-   [#traefik-mesh-companion](https://hashnode.com/tag/traefik-mesh-companion)

## Written by

[Luc Allaire](https://hashnode.com/@wolf361)

@wolf361 · Quebec, Canada

  
[View profile](https://hashnode.com/@wolf361)

Software developer. KMP specialist, DevOps & infra. Building tools for self-hosted infrastructure.

I'm a software developer specializing in Kotlin Multiplatform (KMP) and DevOps infrastructure. I build tools for self-hosted and edge deployments — things that solve real operational pain without requiring Kubernetes or enterprise tooling. Currently working on traefik-mesh-companion, a lightweight Go sidecar that automates DNS and monitoring provisioning for Traefik-based homelabs. Portfolio: https://me.wolf-361.ca

## Responses 1

Markdown supported · ⌘↵ to post

[Edge Ops](https://hashnode.com/@edgecacheops)

[Nov 5](https://hashnode.com/posts/zero-config-dns-and-monitoring-for-your-traefik-homelab/69fe7b02f239332df42533cf/comment/6aebf42118d5d4efb9c54393)

Treating Traefik Host() labels as the only hostname inventory is the ops habit that keeps a homelab edge from rotting. I split public vs mesh traffic by entrypoint rather than inventing a second naming scheme — one entrypoint for TLS-facing routers, another for VPN-only names — so a new compose service either gets a public CNAME or stays internal without a hand-edited DNS sheet. When a router also carries PathPrefix, health checks should hit that path on the same hostname the Host rule advertises; a monitor aimed at / while the app only answers under /api quietly marks a healthy stack as down.

After a label change I confirm which router and entrypoint actually matched, that the public name’s A/AAAA or tunnel target still lands on this edge, and that retired Host() values no longer linger in DNS or status pages. Compound Host() || Host() rules need every hostname provisioned and later cleaned; HostRegexp is fine for routing but cannot drive a static record, so I keep those routers off any auto-DNS path. A deploy that leaves orphan CNAMEs or monitors for containers you removed months ago is usually label drift, not a Traefik crash.