mDNS
What is mDNS?
mDNS (Multicast DNS) lets devices on a local network resolve each other's .local names without a central DNS server, which is how Bonjour, AirPrint and many smart-home devices find printers and speakers nearby. AdminKit's guide explains why local-network discovery protocols like mDNS still need a firewall at the edge.
By AdminKit team, Netbase JSC · Updated
mDNS (Multicast DNS) lets devices on a local network resolve each other’s names, typically ending in .local, without a central DNS server. A device announces its own name over multicast UDP on port 5353, registered with IANA under the service name “mdns”, and any other device on the same network segment can ask “who has this name” and get a direct reply, which is how Apple’s own Bonjour/AirPrint and many smart-home and IoT devices find printers, speakers, and cameras nearby. Because mDNS queries and replies are multicast and unauthenticated, the main risk is scope: it is meant to stay inside a single local network, but misconfigured routers or VPNs that bridge mDNS across network boundaries can leak device names and services to networks that shouldn’t see them, and devices that answer mDNS queries from the public internet become a reflection target for abuse. The Shadowserver Foundation’s Open mDNS Report identifies hosts with mDNS accessible from the internet and records what they disclose, including lists of services that may be reachable through further mDNS queries. mDNS is defined in RFC 6762, and the DNS-SD service-discovery layer built on top of it is defined in RFC 6763.
An mDNS responder reachable from the public internet is abused for reflection the same way an open DNS resolver is, just over a different protocol and port. Unlike ordinary DNS, which relies on a hierarchy of authoritative servers, mDNS resolves names directly between devices on the same local segment.
mDNS is part of AdminKit’s DNS cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What does ".local" mean when I see it on a device?
It's the special domain mDNS uses for local-network names; devices announce and resolve .local names directly over multicast UDP on port 5353, without a central DNS server.
Is it a problem if mDNS leaks outside my local network?
Yes -- mDNS queries and replies are unauthenticated and meant to stay inside one network segment, so a router or VPN that bridges them across network boundaries can leak device and service names, and a device that answers mDNS from the public internet becomes a target for reflection abuse.
What's the difference between mDNS and DNS-SD?
mDNS (RFC 6762) resolves a name to an address on the local network; DNS-SD (RFC 6763) is the service-discovery layer built on top of it that lets a device advertise and find specific services, like printers, by type.
Which devices typically use mDNS?
Apple's Bonjour and AirPrint, along with many smart-home and IoT devices, use mDNS to find printers, speakers, and cameras on the same local network without any manual configuration.