Wednesday, May 27, 2015 [Tweets] [Favorites]

Mac OS X 10.10.4 Replaces discoveryd With mDNSResponder

Benjamin Mayo:

discoveryd would cause random crashes, duplicate names on the network and many other WiFi-relate bugs. In the latest beta, Apple appears to have applied the same fix as the enthusiasts by axing discoveryd completely.

Looking at Activity Monitor on OS X 10.10.4 seed 4, discoveryd is no longer loaded by the system — instead relying on mDNSResponder. The ‘new’ process is really the one Apple used to use pre-Yosemite and did not have these problems.

John Gruber:

The saga of discoveryd is baffling to me. I would love to hear the backstory on how it shipped. And I still haven’t heard a plausible theory on what Apple was hoping to accomplish with it in the first place. What was the point of it?

Nick Heer:

There are two weeks until WWDC, where Apple will probably introduce OS X 10.11. While that won’t be released to the public until, most likely, autumn, 10.10.4 isn’t publicly available yet either. That means that developers, at least, have been using and complaining about discoveryd for about a year, and it’s still busted for consumers.

Furthermore, I haven’t heard a compelling reason for discoveryd’s existence. It must be “better”, in some way, because I can’t think of another reason why Apple would task their engineers with rewriting the networking stack. I always assumed it was to unify iOS and OS X and to enable Continuity features, but those seem to work just fine under mDNSresponder.

Lloyd Chambers:

I’ve had my own inexplicable and disturbing network failures which require disabling networking, then re-enabling it—even as the same local LAN has no issue at all on a 2nd machine. Maybe it’s discoveryd, maybe not but I’m hoping. And then there is the Pathological Network Performance in Apple OS X issue, but I don’t expect Apple to fix that one.

Hopefully, this will eventually fix the problem where I have to reboot my Apple TV before using it or it won’t have network access.

Previously: discoveryd Is Still Buggy, Why DNS in OS X 10.10 Is Broken.

3 Comments

[…] hopefully El Capitan won’t be the hot mess of ill-considered interface experimentation and huge, needless bugs that Yosemite was. To help wash off the Yosemite stink, Apple will be ditching Helvetica Neue, […]

[…] Tech Podcast mentions a German video claiming that the impetus for finally reverting discoveryd to mDNSResponder was a phone call from Vint Cerf to Tim Cook. ATP also recalls the previous story of Logic bugs […]

[…] agree that Apple’s hardware quality continues to be great. Aside from reverting to mDNSResponder, I have not seen an overall improvement in software quality this year. With Mac OS X 10.11, […]

Stay up-to-date by subscribing to the Comments RSS Feed for this post.

Leave a Comment