Why Is mdnsd Draining My Battery and How to Stop It?

Seeing mdnsd near the top of Android battery stats feels scary because the name looks like malware. It is usually mDNS discovery — the same family of tech behind Bonjour/Chromecast finding — working overtime on a noisy local network or because an app will not stop scanning.

This page explains what mdnsd does, why it drains, and how to stop the waste without package-disabler damage.

What mdnsd is doing

mDNS (multicast DNS) lets devices advertise and discover services on your LAN: _googlecast._tcp, printers, some IDE/device bridges, smart speakers, and vendor setup flows. Android’s mdnsd process answers and queries on that channel.

You want it when you tap Cast. You do not want it polling all night because a forgotten IoT app is unhappy.

Trigger	mdnsd behavior	User-visible clue
Chromecast / TV apps	Bursts when you open Cast	Normal short spikes
Smart-home “auto find devices”	Frequent multicast	Idle drain on Wi‑Fi
Flaky mesh / AP isolation	Retries and wakes	Drain only at home
VPN kill-switch flaps	Discovery storms	Spikes when VPN reconnects
After OS update	Reindex / permission resets	24–72 h elevated use

Cross-check general Galaxy idle drain patterns with Samsung battery drain on One UI if Device care blames several system rows at once — mdnsd is often a messenger, not the only villain.

Is it safe? Should you “uninstall” it?

Do not freeze mdnsd with random package tools. You will break Cast, some printing, and device setup, then chase new bugs. Scare blogs that say “delete mdnsd” are in the same genre as panic posts about OEM sync packages — verify first, like we do for com.wssyncmldm.

Treat mdnsd as infrastructure. Reduce clients and network noise.

Fix workflow that actually lowers drain

1. Prove the pattern

For 24 hours note:

• Screen-off drain on home Wi‑Fi vs mobile data only
• Whether Cast or IoT apps were open
• Whether a VPN or “network optimizer” was on

If drain vanishes on LTE with Wi‑Fi off, you are hunting LAN discovery — not a bad battery cell.

2. Deep-sleep the chatty apps

Candidates that love mDNS:

• Multiple smart-home brands’ apps
• Remote desktop / device lab tools
• Old Chromecast / vendor cast helpers you no longer use
• “Network scanner” or “who is on my Wi‑Fi” utilities

On Samsung: Device care → Battery → Background usage limits → Deep sleeping apps. On Pixel-like builds: restrict battery for those apps and disable autostart where the OEM allows.

3. Cast and Nearby habits

• Sign out of cast devices you do not own (Airbnbs, offices).
• Turn off unused Quick Share / Nearby / device scanning features for a test.
• Avoid running three vendor apps that each rescan the LAN every few minutes.

4. Wi‑Fi quality beats process killers

mdnsd retries harder when multicast is lossy:

• AP/client isolation on guest Wi‑Fi can break discovery and cause loops — use the main LAN for Cast, or accept that guest isolation blocks it.
• Dual-band sticky clients that roam every minute create discovery churn.
• Crowded 2.4 GHz IoT SSIDs with dozens of sensors increase chatter.

Stabilize the SSID, reboot the AP once, and retest battery for two days before you assume the phone needs a factory reset.

5. Storage and update pressure

Low storage makes background jobs fail and retry — including network helpers. Free space with the Android storage full steps, install pending system updates, and reboot. Stuck OEM update sync can also look like “mystery system drain” alongside discovery; do not confuse that with mdnsd alone.

Cross-platform note (why iOS friends mention mDNS too)

Apple platforms also use mDNS/Bonjour heavily (AirPlay, Continuity-adjacent discovery). If your household compares phone battery after the same router change, an iPhone may show different process names for similar LAN noise. For iPhone-side battery triage after a major iOS jump, see iOS 26 battery drain fix — useful context when the router, not Android uniquely, started the pain.

What not to do

• Root-only “mdnsd disablers” from random GitHub zips
• Granting Accessibility to cleaners that promise to delete system daemons
• Factory reset as step one
• Blaming mdnsd when Gaming + 120 Hz + 5G weak signal emptied the cell

Developer options and “always scanning” leftovers

If you ever enabled developer toys, audit them:

• Wireless debugging left on outside the house
• Fake location / mock network tools
• Always-on VPN apps that bounce every few minutes
• Packet capture or “Wi‑Fi analyzer” overlays

Each can keep Wi‑Fi and discovery stacks warmer than a normal photo-and-chat day. Turn developer options off entirely for a two-day control test if you are not actively debugging apps.

Also revisit Settings → Location → Wi‑Fi and Bluetooth scanning (wording varies). Scanning helps device find features; it also feeds discovery. Disabling Wi‑Fi scanning for a weekend is a valid experiment when mdnsd and Location together dominate idle drain.

Household changes that suddenly spike mdnsd

Drain that started the week you:

• Added a new mesh node
• Enabled client isolation on guest Wi‑Fi
• Installed a second smart-home brand
• Started working from a café with aggressive captive portals

…is almost never a coincidental battery defect. Change one variable at a time. Park IoT apps, use phone hotspot for an evening, and compare the battery graph. If idle drain collapses off the home LAN, fix the LAN — do not replace the phone battery yet.

When hardware or repair is plausible

If battery graphs look mild but percentage cliffs anyway, or the phone is swollen, you have a cell problem — not multicast. Prep accounts and evidence before a shop visit. Software-only mdnsd drain should improve within 48 hours of culling scanners and fixing Wi‑Fi. Capture screenshots of the battery chart naming mdnsd before any reset so you can prove whether the intervention worked.

Related FixingHacks guides

• Samsung battery drain on One UI
• iOS 26 battery drain fix
• Android storage full
• What is com.wssyncmldm

Bottom line

mdnsd is Android’s mDNS discovery worker. It drains when Cast/IoT apps and messy Wi‑Fi keep multicast busy — not because you need to delete a system daemon. Deep-sleep scanners, clean up Cast clutter, stabilize the LAN, free storage, and update. Leave package disablers out of the story.