mDNS / DNS-SD
Also called Bonjour, Zeroconf, Avahi.
Multicast DNS and DNS Service Discovery: how devices on a local network announce and find each other with no DNS server and no configuration. Dante, NDI, NMOS, OSC discovery and half the show network depends on it working.
Discovery, monitoring, configuration, backups, updates. Useful, and none of it has a deadline of its own.
What kills it. Nothing kills it. That is the problem: with no deadline it has no manners, and it will happily starve everything that does have one. Putting it on a show VLAN is the commonest self-inflicted wound in the industry.
Why this one, and not what the category suggests. Discovery. It is how devices find each other, and it is chatty in a way that matters on a busy VLAN.
Ports
Multicast
224.0.0.251 (IPv4)ff02::fb (IPv6)- Link-local scope: mDNS does not cross a router, which is why devices vanish when someone segments the network.
What goes wrong
What speaks mDNS / DNS-SD (2)
| Product | Direction | Notes |
|---|---|---|
| Dante Controller Audinate |
bidirectional | Dante discovery is mDNS, which is why devices vanish across a routed boundary. |
| Wireshark Wireshark Foundation |
in | Decodes mDNS, the fastest way to prove a discovery problem. |
Open source implementations
- Avahi — C, LGPL-2.1-or-later
Typical use
- Dante device discovery
- NDI source discovery
- Finding a console or media server without knowing its IP
Sources
- RFC 6762: Multicast DNS — IETF primary
- RFC 6763: DNS-Based Service Discovery — IETF primary
Every entry here is maintained by people who run shows.
Edit this entry on GitHub — one file, editable in your browser, and your handle goes on it permanently.
Work at IETF? Confirm or correct this entry — it is free, it stays free, and nothing about it is for sale.