macOS process library · Networking and devices
What is mDNSResponder on Mac?
mDNSResponder turns names like apple.com into the addresses your Mac connects to, for every app. It also runs Bonjour, Apple’s way of finding printers, AirPlay speakers, shared Macs, and other devices on your local network without any setup.
- Part of
- macOS’s DNS resolver and Bonjour service.
- Safe?
- Yes. The copy at
/usr/sbin/mDNSResponderis part of macOS and runs as its own system account. - Can I quit it?
- No. Every app uses it to look up internet addresses, so quitting it breaks connections until macOS restarts it.
The short answer
mDNSResponder is essential and is supposed to be running. Some CPU is normal when apps make lots of lookups or your network has many devices. Sustained high use usually points to a VPN or DNS filter, a chatty device on the network, or an app making an unusual number of requests.
Normal use
What mDNSResponder usually looks like.
On a typical Mac, mDNSResponder uses little CPU and a modest amount of memory. It spikes briefly when you open many web pages at once or when your network changes, like joining new Wi-Fi.
It listens on UDP port 5353 for Bonjour traffic from other devices, which is why you may see it mentioned in network or firewall tools.
Why mDNSResponder uses so much CPU or memory
- Lots of lookups from apps
Browsers with many tabs, apps that sync constantly, and content blockers can make thousands of DNS requests. mDNSResponder handles each one.
- VPNs and DNS filtering apps
Apps that change how DNS works, like VPNs, ad blockers, and parental controls, can cause repeated lookups or reconfiguration.
- A busy local network
Networks full of Bonjour devices such as printers, smart speakers, TVs, and other Macs keep it busy answering and caching announcements.
- Network changes
Switching Wi-Fi networks, waking from sleep, or a flaky connection makes it reset and rebuild its view of the network.
How to calm mDNSResponder down
Start at the top. Each step is more disruptive than the one before.
- Wait a minute after a network change
Spikes after waking or joining a network settle on their own.
- Flush the DNS cache
In Terminal, run
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. This clears cached lookups without stopping the service. - Check VPN and DNS filter apps
Turn off your VPN, ad blocker, or DNS filtering app briefly. If mDNSResponder calms down, update or reconfigure that app.
- Test without your network
Turn off Wi-Fi for a minute. If the CPU drops, the cause is on your network, such as a device flooding Bonjour traffic.
- Restart your router and Mac
A restart clears stuck state on both ends.
Seeing it in Spare
Find what it’s reacting to.
mDNSResponder works for whatever is making network requests. When it climbs, Spare shows which apps, projects, and AI agents were active at the same time, such as a browser with dozens of tabs or a dev server making repeated calls.
Spare lists mDNSResponder as part of macOS and never offers to stop it.
Common questions
About mDNSResponder
Is mDNSResponder a virus or spyware?
No. It’s a core macOS service, and Apple publishes its manual page. It talks to your network because that’s its job.
What is Bonjour?
Bonjour is Apple’s zero-configuration networking. It lets your Mac find printers, AirPlay devices, and other computers on your network automatically. mDNSResponder is the service that runs it.
Can I disable mDNSResponder?
No. Since macOS 10.6 it’s also the system’s DNS resolver, so disabling it would stop every app from reaching the internet.
Why does it show port 5353?
Multicast DNS, the protocol Bonjour uses, runs on UDP port 5353. mDNSResponder listens there for announcements from other devices.
Related processes
Sources: mDNSResponder(8) manual page, Apple Developer: Bonjour. Reviewed October 13, 2026.
Get Spare
Free to use. Yours to explore.
Download Spare for Apple silicon, or explore the MIT-licensed source on GitHub. Free to use, with no subscription or account.
macOS 14+ · Apple silicon · Signed and notarized