Apart from looking bad, this also makes opening network connections and playing iTunes content harder, as you need to connect to the right version of the name or nothing happens. Changing back the computer name in the Sharing pane of the System Preferences usually doesn't take. Under 10.10, this now happens a lot, sometimes getting all the way to nirrti (7). In the pre-10.10 days, once in a blue moon nirrti would rename herself to 'nirrti (2)', presumably because it looked like another machine was already using the name 'nirrti'. We use an old Mac named 'nirrti' as a file- and iTunes server. (Command line tools such as nslookup, host, or dig still work because those use their own DNS lookup code.)ĭuplicate machine names. Turns out that the OS X DNS resolver has stopped working. This is rare, but every once in a while, Safari stops loading any and all websites. Here are some strange networking problems we've observed since installing 10.10: But as of OS X 10.10, the mDNSResponder has been replaced with discoveryd, which does the same thing. 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?įor 12 years, the mDNSResponder service managed a surprisingly large part of our Mac's networking, and it managed this task well.

Obviously, like everyone else, Apple's software has its share of those.īut 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. 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.

Recently, there has been a lot of discussion about the current state of Apple's software quality. Further Reading OS X 10.10 Yosemite: The Ars Technica Review

Network connect mac 10.10