Menu
When you install Bonjour for Windows you can resolve any ".local" mDNS name from anywhere in the system.
For example, you can "ping some_computer.local" and mDNSResponder.exe (Bonjour/mDNS Daemon) will respond.
However, mDNS operates on port 5353 so how does Windows know how to resolve these DNS queries?
Is mDNSResponder.exe hooking into the Windows DNS Resolver somehow?
928
Devices and services from Microsoft, Apple, Google, and Amazon all use mDNS in some capacity.
When an mDNS client needs to resolve a hostname, it sends an IP multicast query message that asks the host having that name to identify itself. That target machine then multicasts a message that includes its IP address. All machines in that subnet can then use that information to update their mDNS caches.
Multicast DNS (mDNS) provides a naming service system that is easy to set up and maintain, for computers on a local link. All participating network devices on the same local link perform standard DNS functions, using multicast DNS rather than unicast, and do not need a unicast DNS server.
- Disable mDNS (Apple Bonjour or avahi-daemon) service if you are not using it. Is the easiest and the most effective solution. - Configure your firewall to filter inbound connections to your server UDP/5353, and only allow the trusted network IPs/hosts that need to contact your mDNS service to access it.
Bonjour for Windows allows any software using the standard name resolution APIs to resolve mDNS names; it does so by registering a DLL (mdnsnsp.dll) as a namespace provider using WSCInstallNameSpace.
The corresponding code is included in the mDNSResponder source (in particular, look at the mdnsNSP and NSPTool components).
99
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
