What Is mDNS and Why Does It Matter for Network File Sharing?
mDNS is the technology that lets devices find each other on a local network without a DNS server. When it breaks, computers disappear from your network. Here is how it works.
The Problem mDNS Was Designed to Solve
On the internet, every domain name (like google.com) is translated to an IP address by a DNS server. There is a global infrastructure of DNS servers that handles this. But inside your office — between the machines on your local network — there is no such infrastructure. There is no DNS server resolving DESKTOP-OFFICE1 to 192.168.1.45.
Without something to handle that translation, machines on your local network cannot find each other by name. They can only communicate by IP address — which you have to look up manually, write down, and re-check every time a machine gets a new IP from the router.
mDNS (Multicast DNS) solves this. It allows devices on a local network to announce their names and discover other devices without any centralised server. When a device needs to find DESKTOP-OFFICE1.local, it sends a multicast packet to the entire local network asking "who has that name?" The owner of that name responds directly.
Who Invented mDNS and Who Uses It
mDNS was developed by Apple alongside its Zeroconf networking project in the early 2000s. The protocol is standardised as RFC 6762.
It is the technology behind:
- Apple Bonjour — Apple's implementation of mDNS and related protocols. macOS uses Bonjour for AirDrop, AirPlay, App Store discovery, and connecting to shared folders and printers. Every Mac runs Bonjour automatically.
- Avahi — The open-source Linux implementation of mDNS. Used by most Linux distributions for network discovery.
- Windows mDNS — Windows 10 and 11 include a native mDNS stack used for certain discovery tasks, though it is less pervasive than Bonjour on Mac.
- IoT devices — Smart TVs, smart speakers, Chromecast, Philips Hue, network printers, and most smart home devices use mDNS for local discovery.
How mDNS Works: The Technical Detail
When a device joins a network, it registers a name for itself in the .local domain (e.g., macbook-pro.local or DESKTOP-WORK.local). It does this by sending a multicast DNS registration packet to the entire network.
When another device wants to find it, it sends a multicast DNS query packet to the reserved multicast address (224.0.0.251 for IPv4, ff02::fb for IPv6) on port 5353, asking for the address of macbook-pro.local. The named device sees it and responds directly.
No server is involved. No configuration is needed. It works as long as multicast traffic can flow across the network.
Why mDNS Breaks — and What Breaks With It
Three common conditions break mDNS:
1. Managed switches with IGMP snooping misconfigured Multicast traffic can be blocked at the switch level if IGMP (Internet Group Management Protocol) snooping is enabled but not properly configured. The switch filters the multicast packets that mDNS depends on, and devices become unable to discover each other. This is common on enterprise-grade managed switches in office environments.
2. Different VLANs or network segments mDNS multicast packets do not cross router boundaries by default. If your printers are on a separate VLAN from your workstations, mDNS discovery fails between them. Fixes include mDNS repeater/proxy services (like Avahi in proxy mode, or router firmware that supports mDNS bridging between VLANs).
3. Windows Defender Firewall blocking multicast Windows Firewall can block the incoming mDNS responses, causing Windows to not see mDNS announcements from other devices on the network.
mDNS and Windows Network Discovery: The Connection
Windows' own "Network Discovery" (the feature that shows PCs in the Network folder) uses a different protocol stack — SSDP (Simple Service Discovery Protocol) and WS-Discovery (Web Services for Devices). This is why computers disappear from Windows' Network folder independently from whether mDNS is working.
However, many modern LAN file sharing tools — including LocalSend and Oxolan — use mDNS for their own peer discovery rather than relying on Windows' SSDP-based discovery. This makes them work even when Windows' own Network folder is showing nothing.
mDNS on Mac vs Windows
On Mac: Bonjour runs continuously in the background. macOS .local name resolution works out of the box for any device that registers via mDNS. AirDrop, AirPlay, shared folders, and printer discovery all use it. When a Mac connects to a network, it is discoverable by other Bonjour-enabled devices almost immediately.
On Windows: The mDNS stack exists but is less integrated into the user experience. Windows resolves .local names for specific features (like finding printers) but does not give users a clean directory of mDNS-registered devices. Windows also runs SSDP/UPnP in parallel for its own Network folder discovery, creating two separate discovery systems.
Cross-platform implications: When a Mac and Windows PC are on the same network, the Mac can typically find the Windows machine's name via mDNS (registered by Windows' own mDNS service). Windows can usually find Macs in the Network folder if Bonjour Print Services for Windows is installed. Using a tool that explicitly uses mDNS (like LocalSend) resolves cross-platform discovery more reliably.
Why Application-Level Discovery Is More Reliable Than mDNS Alone
File sharing applications that use mDNS for discovery are more reliable than ones that depend on Windows' Network folder, but mDNS is still a network-layer protocol that can be blocked by firewall rules, switch configurations, or VLANs.
Some tools maintain their own discovery mechanism that combines mDNS with direct IP scanning as a fallback, providing more reliable peer detection regardless of network infrastructure.
Frequently Asked Questions
Does mDNS work over WiFi? Yes. mDNS works on both wired and wireless networks. The multicast traffic is carried by the WiFi infrastructure like any other network traffic.
Is mDNS secure? mDNS is limited to the local network — it does not traverse the internet or router boundaries by default. Device names and service announcements broadcast via mDNS are visible to any device on the same network segment. On trusted office networks, this is not a practical concern.
Can I use mDNS names to access network shares?
On Windows, you can use \\HOSTNAME.local\ShareName to access a share by mDNS name if both machines have compatible mDNS stacks. Mac-to-Mac sharing via mDNS names works natively. Cross-platform reliability varies by Windows version.
Why do I see devices on mobile but not on my Windows PC? Mobile devices (iOS, Android) implement mDNS natively and tend to discover each other reliably. Windows' SSDP-based Network folder is a different discovery mechanism that may not find the same devices. Using an app that explicitly uses mDNS on Windows (rather than relying on the Network folder) will show the same devices your phone sees.
Done troubleshooting Windows?
Oxolan handles file sharing so you never have to think about this again.
Get Oxolan for Windows