Recently, there has been a lot of discussion about the current state of Apple’s software quality. Anyone with even a passing familiarity with development knows that bugs are par for the course, and most people aren’t bothered by small, day-to-day bugs that are fixed within a reasonable timeframe. Obviously, like everyone else, Apple’s software has its share of those. But there’s another category of bug—glaring, perplexing bugs that couldn’t possibly have escaped the attention of the software engineers in question, let alone the quality assurance department. Such issues exist, and sometimes they go unfixed for months. Or years. Or ever. Hopefully, the set of network issues with OS X 10.10 described below won’t fall into this column, but they do raise an obvious question: why? For 12 years, the mDNSResponder service managed a surprisingly large part of our Mac’s networking, and it managed this task well. But as of OS X 10.10, the mDNSResponder has been replaced with discoveryd, which does the same thing. Mostly. Here are some strange networking problems we’ve observed since installing 10.10: Read 18 remaining paragraphs | Comments
View article:
Why DNS in OS X 10.10 is broken, and what you can do to fix it
