mDNSResponder not resolving local network hosts for ping and SSH

Question

Level 1

9 points

mDNSResponder not resolving local network hosts for ping and SSH

Recently - and I don't know if that's an Apple or an environment change - mDNSResponder using programs (eg `ping`, `ssh` have stopped resolving hosts on my local networks. Thus, I can get name mapping info from `dig`, but cannot ssh into local linux boxes easily.

I've tried:

`sudo killall -HUP mDNSResponder`

but this doesn't seem to make any difference.

I've also tried commenting out google's dns address as I read that this can be preferred by mDNSResponder as it supports dnssec, whereas my internal router (Fritzbox) doesn't.

Any thoughts/suggestions?

MacBook Pro 15″, macOS 10.15

Posted on Aug 12, 2026 4:54 AM

Reply

Answer 1

Top-ranking reply

PreCognition

Level 4

2,908 points

Aug 12, 2026 5:12 AM in response to mtimc

I’d check the actual hostname first. If these Linux boxes are using names ending in `.local`, that may be the problem. macOS reserves `.local` for Bonjour/mDNS rather than normal unicast DNS.

Also, `dig` isn’t a good comparison with `ping` or `ssh` on macOS because it doesn’t use the same native name-resolution path.

Try:

scutil --dns

and see which resolver/search domain macOS has for your Fritzbox network. I’d also test the full hostname rather than just the short host name.

What exact name works with `dig` but fails with `ping` — for example `server`, `server.local`, or `server.fritz.box`? That would help narrow it down.

Reply

Answer 2

BobHarris

Level 9

58,189 points

Aug 12, 2026 6:15 AM in response to mtimc

Not sure if Sonoma got this, but some macOS updates added that you needed to give local network access to apps like Terminal to talk to other systems on your LAN.

Reply

Answer 3

etresoft

Level 9

58,842 points

Aug 12, 2026 6:39 AM in response to mtimc

Those are low level tools. You haven't installed anything that rhymes with "brew" have you?

Reply