Thrum

What is mDNSResponderHelper on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.

mDNSResponderHelper is a small Apple helper that performs the few privileged tasks that mDNSResponder, the DNS and Bonjour daemon, is not allowed to do itself. It starts on demand, runs briefly and normally uses almost no CPU. It is part of macOS and safe.

mDNSResponderHelper at a glance

mDNSResponderHelper
Made byApple (part of macOS, Bonjour and DNS)
TypeSystem helper daemon
Location/usr/sbin/mDNSResponderHelper
Runs asroot
Started bylaunchd job com.apple.mDNSResponderHelper.reloaded
Can you quit it?Not usefully. launchd starts it again the next time mDNSResponder needs it.

What is mDNSResponderHelper?

The man page calls it the mDNS privilege separation helper. mDNSResponder runs as the limited _mdnsresponder account so that a bug in network-facing code cannot take over the Mac. The rare operations that need root are handed to mDNSResponderHelper, which runs as root and accepts requests only through its own launchd service, com.apple.mDNSResponder_Helper.

Splitting work this way is called privilege separation: the part that reads untrusted packets from the network has few rights, and the part with full rights never reads those packets.

Is mDNSResponderHelper safe?

Yes. It is part of macOS in /usr/sbin on the read-only system volume, and launchd starts it from an Apple launch daemon. The man page notes that users should not run it manually.

Why does mDNSResponderHelper use so much CPU?

How much CPU is normal for mDNSResponderHelper?

Typical use is 0% CPU. It is often not running at all and appears for a moment when needed.

Any sustained CPU use is unusual and almost always comes with high CPU in mDNSResponder itself.

What should you do if mDNSResponderHelper is busy?

  1. Look at mDNSResponder first. In Activity Monitor, check whether mDNSResponder is also busy. The helper only works for it, so the cause is the same.
  2. Check for frequent network changes. A Wi-Fi connection that keeps dropping, or a VPN that reconnects every few minutes, makes the DNS setup rebuild repeatedly. Run scutil --dns after each change to see what is applied.
  3. Restart the Mac. If the helper stays busy with no network changes, a restart clears its state. launchd starts it again only when it is needed.

When should you worry about mDNSResponderHelper?

Sustained CPU use with a stable network is not expected and is worth a restart. A copy of mDNSResponderHelper outside /usr/sbin would not be Apple's.

How do you check mDNSResponderHelper in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type mDNSResponderHelper in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every mDNSResponderHelper process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'mDNSResponderHelper' | grep -v grep

How can Thrum help with mDNSResponderHelper?

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 mDNSResponderHelper 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 mDNSResponderHelper

Why does mDNSResponderHelper run as root?

It exists to do the few privileged tasks mDNSResponder needs, so that mDNSResponder itself can run as a limited account.

Is it the same as mDNSResponder?

No. mDNSResponder does the DNS and Bonjour work; mDNSResponderHelper is a separate process it calls for root-only tasks.

Sources