[Swordmaker]

Apple releases security update for mDNSResponder for non-up-to-date devices. Check your software update to see if there is a security update for your device and install the latest if it's there. If you don't, the older DNS responder is susceptible to being hijacked by hackers pretending to be what they are not. — PING!

Apple Security
Ping!

The latest Apple/Mac/iOS Pings can be found by searching Keyword "ApplePingList" on FreeRepublic's Search.

If you want on or off the Mac Ping List, Freepmail me

[ImJustAnotherOkie]

I pasted this from another source.

http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-you-can-do-to-fix-it/

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?