DNS Resolution Failures in macOS 26 and 27
Sporadically (once every week or two) on macOS 26, domain name resolution will just abruptly stop working. But, it gets worse. I recently updated to macOS 27.2, and now the problem occurs multiple times an hour.
That is, name resolution fails if done through Apple’s libraries – through
digornslookupit continues to work just fine, which means things likepingalso work just fine, but e.g.curland Safari do not.[…]
I’ve been seeing this issue on multiple completely independent Macs and networks for many months now – and now, as noted, it’s a thousand times worse in macOS 27[…]
He has some workarounds like killing configd.
Previously:
- Mac OS X 10.10.4 “Improves Networking Reliability”
- Mac OS X 10.10.4 Replaces discoveryd With mDNSResponder
- Why DNS in OS X 10.10 Is Broken
4 Comments RSS · Twitter · Mastodon
Remember the days when Panther would hang for 30 seconds whenever it saw an AAAA record? Memories.
I'm pretty sure I see this problem fairly frequently in macOS 15 Sequoia as well as iOS 18. This bug has been a thing for a while and really makes Apple devices feel like they're finicky when trying to view websites. Might not be the same exact bug, but on iOS, I force quit Safari a lot to force it to connect to websites more quickly.
When this happens.
I close Safari
Open the terminal & run this below - most of the time it works fine after that.
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
