Announce service domains via mDNS

[schildbach]

I'd like Traefik to announce a domain within my local network via Multicast DNS (Avahi/Zeroconf/Bonjour). Note this is explicitely not requiring a DNS server like #1191 is suggesting.

This would make it a lot easier for deploying multiple docker/docker-compose services on a small home network with just one server. E.g. Node-RED, Riot-Web, Nextcloud could be published as nodered.local, riot.local, nextcloud.local, etc. Home networks usually don't run their own internal DNS server, and services (e.g. Printers, Sensors, etc.) usually announce themselves in a P2P manner (mDNS).

[traefiker]

Hi! I'm Træfiker 🤖 the bot in charge of communication regulation.

Thanks for your interest in Traefik!

Issue templates help us help you by providing all necessary information.

Please edit your issue and use the available templates:

• Feature request
• Bug report

And remember: each time someone ignores the template, a cute little bunny dies.

#SaveTheCuteBunny ❤️ 🐰 ❤️

[mpl]

Hi @schildbach ,
In addition to respecting the template, could you please describe a specific use-case of a problem, detailing how mDNS would help and fix the problem (just as if we did not know how mDNS works, which is pretty much the case)?

[schildbach]

I thought I had described a usecase in the second paragraph. mDNS is decentralized DNS. Any host or device in your local network can publish (broadcast) DNS records, that is hosts or services. Others use these broadcast to resolve named hosts or services.

Now, if you want to deploy e.g. Node-RED in your local network (on a server), you would want to announce a host for that app, e.g. "nodered.local". Traefik would be responsible for this; currently I'm doing this manually. Traefik would use SNI to destinguish between multiple these apps based on mDNS, just as it does already for normal DNS.

[mpl]

Sorry, but we do not think that feature belongs among the roles of a reverse-proxy.

[spacemud]

This is precisely what I'm trying to do at the moment - understandable that it's not considered to be within the scope of Traefik itself.

I wonder if you were able to find a solution @schildbach ? I'm struggling to create a config that can handle mDNS domains.

[schildbach]

@spacemud I've manually configured one mDNS domain per service. You might want to read avahi/avahi#40 as the intuitive way to add the domains /etc/avahi/hosts cannot be used either. See the discussion for workarounds via systemd.

[viraptor]

This can be done externally rather than in traefik itself. I've created this project which may satisfy what you're after. https://gitlab.com/viraptor/docker_mdns

[schildbach]

I think the solution I (and probably others) are looking for is an automatic one. As soon as a service is brought up that announces a .local domain to Traefik, the mDNS domain shall be broadcast. I agree that this is probably out of focus for Traefik itself – on the other hand I currently don't see another component that could automate this.