Ranger Try it free

What is mDNSResponder on a Mac, and why is it so busy?

In short: mDNSResponder looks up names for every app on your Mac, turning an address like apple.com into the numbers computers use, and finds printers, speakers and other devices on your home network. Every app's lookups go through it, so it is one of the busiest programs on the network. It's essential: block it and nothing can find anything.

Apple's description: mDNSResponder implements "Multicast DNS and DNS Service Discovery" and is also "the system-wide Unicast DNS Resolver". It performs DNS queries "on behalf of client processes, and maintains a cache of the replies" (man mDNSResponder).

Two jobs, in plain words

Looking up names (DNS). Computers connect to numeric addresses. When an app wants to reach a site by name, it asks mDNSResponder, which asks a DNS server (usually your router, your internet provider, or a service you chose) and remembers the answer for a while. Because every app on the Mac does this, mDNSResponder's connections are mostly to your DNS server, all day long.

Finding devices nearby (Bonjour). Printers, AirPlay speakers, other Macs and smart TVs announce themselves on your local network. mDNSResponder listens for these announcements on UDP port 5353 and answers questions about your Mac (man mDNSResponder). That's how a printer appears in the print dialog without you typing its address.

It also reads your hosts file

The hosts file, /etc/hosts, is a short list of names and addresses on your Mac. According to its manual page, it "is read by mDNSResponder" and used alongside the answers from DNS (man hosts). That's why blocking a site through the hosts file works in every app, and why the usual way to make a change take effect is to tell mDNSResponder to clear its cache (Apple):

sudo killall -HUP mDNSResponder

Despite its name, killall here only sends mDNSResponder a signal, and this is the command Apple gives for resetting the cache. Our guide to editing the hosts file has the details.

Is it safe?

The genuine mDNSResponder is Apple's and lives at /usr/sbin/mDNSResponder, a folder protected by System Integrity Protection (Apple). To check where the running copy lives, type this in Terminal:

ps -ax -o comm | grep mDNSResponder

Should you block it?

No. Without mDNSResponder, no app can turn a name into an address, so practically nothing on the Mac can connect. If a lot of lookups worry you, the question to ask is which apps are making them, and that is what a firewall that records connections by app is for.

How Ranger handles it

Ranger never blocks mDNSResponder; name lookups are one of a handful of macOS services that every other app depends on. Ranger does use mDNSResponder's answers: they are how it knows which name an address belongs to, so Traffic can show example.com instead of a row of numbers, and so a rule on a domain applies whichever address the domain uses that day.

For the other system programs you may meet in a list of connections, see our guides to trustd, apsd, nsurlsessiond and rapportd.