Recently I spent part of the weekend to build a small companion for Traefik. Beacon automatically scrapes the Host() part of Traefik rules and announces them via mDNS in the local network.
The idea is to use this in our greenhouse, hence the greenery in the name. Shooting for a small solar powered RPi Setup, and this gives me easy acces via local Wi-Fi e.g. for debugging or sensors/bridges.
I hope to spend some time around the ideas of air gapped/remote self hosting.



I guess this can be useful when you can’t change DNS on the local router.
But wouldn’t announcing
*.local.domainfor the server that Traefik runs on accomplish the same?Totally. It’s even useful if you can change DNS, because it allows you to quickly throw something behind Traefik and access it right away. It’s like a lab convenience tool, that allows you to skip IPs and just use names without much effort.
I’m not sure mDNS allows you to publish *.local. And otoh you might want two of these servers :)
You’re right I don’t think it can, can only advertise explicit labels.