Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #68393

Re: DNS in Yosemite

Show all headers | View raw

In article <1ly7648.lsq0i21ds1buxN%dempson@actrix.gen.nz>, David Empson
<dempson@actrix.gen.nz> wrote:

> Otto Pylot <otto@bogus.address.com> wrote:
> 
> > In article <54b4354c$0$29405$c3e8da3$e074e489@news.astraweb.com>, JF
> > Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> > 
> > > On 15-01-12 15:48, Neill Massello wrote:
> > > > Yet another article concerning the decline of Apple's software quality.
> > > > 
> > > >
> > > > <http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-
> > > > and-wh at-you-can-do-to-fix-it/>
> > > > 
> > > 
> > > Hey ! I am mad. I was just about to post the same :-)
> > > 
> > > Also deals with the "duplicate machine name" problem that was discussed
> > > here a couple of times.
> > > 
> > > The Readers Digest version: Apple rewrote mDNSresponder from scratch
> > > into "discoveryd" written in C++ instead of C, so thei is a V1.0 piece
> > > of software, clearly untested.
> > 
> > So what are us "normal" users to do?
> 
> Wait. According comments on that article, at least some of these issues
> have been fixed in 10.10.2, which I hope will be released in the next
> couple of weeks.
> 
> The suggestion to install an old mDNSResponder to work around the
> problems seems risky, since that results in an unsupported system
> configuration which may introduce different problems. At a minimum, if
> you were to do this, it would be a good idea to restore the normal
> configuration before installing any 10.10.2 or later update, or any
> security update.
> 
> If you don't need to connect in to your computer using the various
> remote access features that seem to be problematic (which you probably
> don't on a MacBook Air), then that just leaves two potential annoyances:
> 
> 1. Random failures to resolve DNS names due to the DNS resolver
> malfunctioning.
> 
> I've been running Yosemite full time for about three months and I'm not
> aware of encountering this one. I can't think of any instances among
> locals I've helped either.
> 
> 2. Duplicate machine names resulting in a (2) or higher suffix.
> 
> I haven't seen this myself, even though my system meets what appear to
> be all the necessary trigger conditions: "Wake for network access" is
> enabled, some sharing services are enabled, and I have devices on my
> network which can act as Bonjour sleep proxies (an Apple TV and two
> Airport base stations).
> 
> I am aware of other people on the Internet complaining about this, but I
> haven't seen it on any computers running Yosemite for people I'm
> supporting.
> 
> If it does affect you, an easy workaround is to turn off "Wake for
> network access" until Apple releases a Yosemite update which fixes this,
> since that will stop the computer from using a Bonjour sleep proxy (if
> there is one on the network). The name conflict appears to be caused by
> Yosemite seeing the computer's name from the Bonjour sleep proxy as a
> duplicate after it wakes from sleep.
> 
> > I'm not comfortable at all with using terminal to find and copy the
> > mDNSresponder files from 10.9 to 10.10. Not to mention the fear of
> > imploding if there's a problem with a future update. I have a new MacBook
> > Air coming in a week or so already configured with Yosemite.
> 
> Possibly bad timing on that computer purchase. At CES, Intel announced
> the next generation of processors suitable for Apple to update the
> MacBook Air, which will probably happen in February unless they need to
> wait for reasons such as some other component being delayed, software
> support to be ready, or to sync with another product release.

Unfortunately we didn't really have a choice. She needs a computer now
and sharing my current MacBook Air wouldn't work. I'm not a speed
junky, leave multiple apps open, or do any sort of heavy duty
processing so I'm hoping the new 8/128 Air will tie me over for the
next couple of years. I like my mid-2011 now so this will just be a
moderate improvement over what I have and will be newer.

-- 
Deja Moo: I've seen this bullshit before. Please respond to: scasse@invalid.net
replacing invalid with sonic.

Back to comp.sys.mac.system | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

DNS in Yosemite nmassello@yahoo.com (Neill Massello) - 2015-01-12 13:48 -0700
  Re: DNS in Yosemite JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-01-12 15:57 -0500
    Re: DNS in Yosemite Otto Pylot <otto@bogus.address.com> - 2015-01-12 19:39 -0800
      Re: DNS in Yosemite dempson@actrix.gen.nz (David Empson) - 2015-01-13 23:29 +1300
        Re: DNS in Yosemite JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-01-13 11:42 -0500
          Re: DNS in Yosemite dempson@actrix.gen.nz (David Empson) - 2015-01-14 12:02 +1300
            Re: DNS in Yosemite JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-01-13 18:48 -0500
              Re: DNS in Yosemite dempson@actrix.gen.nz (David Empson) - 2015-01-14 16:05 +1300
                Re: DNS in Yosemite JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-01-14 10:37 -0500
                Re: DNS in Yosemite Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-01-17 02:39 +0000
            Re: DNS in Yosemite Alan Baker <alangbaker@telus.net> - 2015-01-13 18:39 -0800
              Re: DNS in Yosemite dempson@actrix.gen.nz (David Empson) - 2015-01-14 16:05 +1300
                Re: DNS in Yosemite Alan Baker <alangbaker@telus.net> - 2015-01-13 19:13 -0800
                Re: DNS in Yosemite dempson@actrix.gen.nz (David Empson) - 2015-01-14 17:16 +1300
        Re: DNS in Yosemite Otto Pylot <otto@bogus.address.com> - 2015-01-13 17:12 -0800

csiph-web