What is mDNSResponder, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
mDNSResponder is the macOS daemon that turns names like apple.com into IP addresses for every app, and that runs Bonjour, the system that finds printers, speakers and other Macs on your local network. It gets busy when apps make many DNS lookups or when the local network is full of Bonjour devices. It is part of macOS and must keep running.
mDNSResponder at a glance
| mDNSResponder | |
|---|---|
| Made by | Apple (part of macOS, Bonjour and DNS) |
| Type | System daemon |
| Location | /usr/sbin/mDNSResponder |
| Runs as | _mdnsresponder (a system account) |
| Started by | launchd job com.apple.mDNSResponder.reloaded |
| Can you quit it? | Not usefully. Every name lookup on the Mac goes through it, so launchd starts it again at once and network apps stall in between. |
What is mDNSResponder?
The man page describes mDNSResponder as the Multicast and Unicast DNS daemon. It has two jobs. First, it is the system-wide DNS resolver: when Safari, Mail or any other app needs the address of a server, it asks mDNSResponder, which sends the DNS query and keeps a cache of the replies. Second, it implements Multicast DNS and DNS Service Discovery, the standards behind Bonjour. It listens on UDP port 5353 and answers questions from other devices on the local network.
Bonjour is what lets your Mac see a network printer, an AirPlay speaker or another Mac's shared folders without typing an address. Apple's developer page calls it zero-configuration networking. mDNSResponder runs as the _mdnsresponder system account and receives requests through the /var/run/mDNSResponder socket. A helper, mDNSResponderHelper, does the few tasks that need root.
Is mDNSResponder safe?
Yes. mDNSResponder is part of macOS, lives in /usr/sbin on the read-only system volume, and is signed by Apple with the identifier com.apple.mDNSResponder. Its traffic to port 5353 on your local network is normal Bonjour traffic.
Why does mDNSResponder use so much CPU and network?
- Apps making many DNS lookups. Browsers, mail clients, sync tools and developer tools can look up hundreds of names a minute. Each lookup passes through mDNSResponder, so its CPU follows the busiest app.
- A busy local network. On a network with many printers, smart speakers, TVs and computers, Bonjour announcements and questions arrive constantly. mDNSResponder reads and answers each one.
- Network changes. Joining a Wi-Fi network, waking from sleep, or connecting or disconnecting a VPN changes the DNS settings. mDNSResponder flushes and rebuilds its cache and re-announces this Mac's Bonjour services.
- Apps browsing for devices. An app that keeps searching for AirPlay receivers, printers or game peers keeps mDNSResponder browsing the network on its behalf.
- VPN or DNS filtering software. VPNs, content filters and DNS proxy apps can route every lookup through extra steps. If one of them misbehaves, lookups are retried and mDNSResponder works harder.
How much CPU is normal for mDNSResponder?
Typical use is near 0% CPU with short spikes when apps open many connections. A few percent for a while after waking the Mac or switching networks is expected.
mDNSResponder staying above 20 to 30% CPU for many minutes while you are not doing anything networked is not typical, and usually points to one app or network device generating a flood of requests.
How do you stop mDNSResponder from using so much CPU?
- Find the app making the lookups. In Activity Monitor's Network tab, sort by Sent Packets and see which app is busiest at the same time. Quitting that app is the quickest test.
- Flush the DNS cache. If names resolve wrongly or slowly, run
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderin Terminal. This clears the cache without stopping Bonjour. - Check your DNS settings. Run
scutil --dnsto see which DNS servers and search domains are active. A VPN or old configuration profile that adds unreachable servers makes every lookup wait and retry. - Look at Bonjour traffic. Run
dns-sd -B _services._dns-sd._udpto list the Bonjour service types on your network, and press Control-C to stop. A very long, changing list means a noisy network. - Test without VPN or filter apps. Disconnect any VPN and turn off DNS filtering or ad-blocking apps for a few minutes. If mDNSResponder calms down, update or reconfigure that app.
When should you worry about mDNSResponder?
Look closer if mDNSResponder stays high for hours with your apps closed, or if web pages regularly take seconds to start loading. Both suggest a DNS server that is not answering or a network device flooding Bonjour traffic.
A process called mDNSResponder running from anywhere other than /usr/sbin would not be Apple's.
How do you check mDNSResponder in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type mDNSResponder in the search field. The CPU tab shows its % CPU. The Network tab shows its Sent Bytes and Rcvd Bytes. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every mDNSResponder process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). nettop shows its live network traffic.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'mDNSResponder' | grep -v grep
nettop -p mDNSResponder
How can Thrum help with mDNSResponder?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when mDNSResponder is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about mDNSResponder
Can I disable mDNSResponder?
No. It is the Mac's DNS resolver, so without it apps cannot find any server by name. On current macOS it is protected by System Integrity Protection and cannot be unloaded.
Why is mDNSResponder talking to devices on my network?
That is Bonjour. It answers questions such as which printers or AirPlay receivers are present, using multicast on UDP port 5353, which Apple lists for Bonjour, AirPlay, Home Sharing and printer discovery.
Does killall -HUP mDNSResponder stop it?
No. The HUP signal tells it to clear its cache. The process keeps running.
Sources
- mDNSResponder(8) man page: run man mDNSResponder in Terminal
- Apple Developer: Bonjour
- Apple Support: TCP and UDP ports used by Apple software products