Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I hope this is the first of many "fixes" they dedicate themselves to making in version 10.11.x. Supposedly 10.11 is going to offer more in the way of improvements to existing structure than new "features".

I have been running the Mavericks version of mDNSResponder on Yosemite since the second week of Yosemite, with discoveryd disabled. It works flawlessly (still).

Now, if they'd just take a look at ntpd as well.
 
mDNSResponder in prerelease Yosemite is not mDNSResponder-522.92.1

… Apple has reverted back to using the earlier mDNSresponder process that was used before discoveryd was implemented with OS X Yosemite. …

Code:
sh-3.2$ sw_vers ; strings /usr/sbin/mdnsresponder | grep 522.92.1
ProductName:	Mac OS X
ProductVersion:	10.9.5
BuildVersion:	13F1077
/SourceCache/mDNSResponder/mDNSResponder-522.92.1/mDNSMacOSX/mDNSMacOSX.c
mDNSResponder-522.92.1
/SourceCache/mDNSResponder/mDNSResponder-522.92.1/mDNSMacOSX/LegacyNATTraversal.c
@(#) mDNSResponder mDNSResponder-522.92.1 (Jul 27 2014 17:31:49)
sh-3.2$

Is it the last version from Mavericks …

No.

Please compare the Terminal output above with the output below.

Code:
sh-3.2$ strings /Volumes/Yosemite/usr/sbin/mdnsresponder | grep 522.92.1
sh-3.2$

… roll back older versions …

Please see above, it's not 522.92.1

----

Off-topic

… Doesn't look like standard UI, what did you do to get it like that?

At https://forums.macrumors.com/search/?searchthreadid=1751546 seek: Flavours
 
and unless anyone took at look at Activity Monitor no one would have ever known. :D

The fact that the name of my Apple TV would stop incrementing would have given it away.

Currently up to: John's Apple TV (5) (since the last "reboot everything" episode.)
 
So that's why my MBA wifi sometimes would disconnect when it's been idling for a few minutes, it would take some time to reconnect. I thought it was just the Airport Express that I connected to a radius auth that's causing it.

I hope this gets out soon.
 
progress? ignoring the EPIC FAIL for the moment, whats new in the DNS front since like... al gore invented the internet? :D

jokes aside... this surely looks like someones pet project going bad. :cool:

That Al Gore joke is getting old, wel dns news is not a frequent item but there are exaples (apart from "new" record types aka AAAA) , dnssec and nsec3 iirc might be more but it's late and i don't feel like looking it up, sorry for beeing lazy
 
I just wonder what the common denominator is. 2011 17" MB Pro with Yosemite and even with the developer previews and I never once had the issue. I have a 4th gen Airport Base Station and at work we use a more recent Base Station. At my parents they have an Xfinity wireless router, but I rarely use it there. Not one Wi-Fi issue.

I did have that issue with duplicate network names however. I am also curious if they just renamed it mDNSresponder as a placebo. Hmmm....

That's the thing - from what I've read, it's mostly newer hardware. I have a late 2013 MBPr 15" and have often wondered if the internal wifi is faulty or the IOS is faulty - perhaps a combination of both. When I went from 10.10.1 to 10.10.2 it crippled my wifi so I have been back on 10.10.1 waiting it out.
This article is the exact story I have been waiting to see - possibly a legitimate attempt to fix one massive clusterfk.
 
so far today since installing the latest build i've had 3 crashes all tied to safari - logging in to to amazon, clicking on a link in huff post and going to eBay.
After reading this I decided to go from 10.10.3 and try the public beta, I was hoping everything would be great, but, my mac also crashed while using safari (it just froze this time). My mac hasn't crashed for years until 10.10.3, and now the current 10.10.4 public beta. :( It's possible there were other changes to the OS based on Discoveryd, so apple may not be done "untying" it. I do hope they back off Discoveryd for now, I don't like my mac crashing just out of doing nothing special.
 
Still wi-fi issues :(

I installed beta with mDNS responder thinking my wi-fi problems will go finally. Nah. Still the same!

After 2-5 minutes 5GHz connection to airport drops (visually it is there, but internet stops working).

Tried
- 2 different AirPort Extremes.
- fresh install
- SMS, Pram etc.
- everything recommended on the web
- disabling airdrop
- disabling handoff

Cannot disable bluetooth as need it for keyboard.

I also have linksys access point (connected to the same network). Connection never drops on it.

Have to use ethernet at work!

I never had issues with Yosemite wi-fi before 10.10.3. Read a lot about it but my mbp was just fine. Problems started once i installed 10.10.3 beta.
 
I installed beta with mDNS responder thinking my wi-fi problems will go finally. Nah. Still the same!

After 2-5 minutes 5GHz connection to airport drops (visually it is there, but internet stops working).

Tried
- 2 different AirPort Extremes.
- fresh install
- SMS, Pram etc.
- everything recommended on the web
- disabling airdrop
- disabling handoff

Cannot disable bluetooth as need it for keyboard.

I also have linksys access point (connected to the same network). Connection never drops on it.

Have to use ethernet at work!

I never had issues with Yosemite wi-fi before 10.10.3. Read a lot about it but my mbp was just fine. Problems started once i installed 10.10.3 beta.

With the 5Ghz, do you specify a channel on the router or do you let it auto-select one? if you use automatic channel selection then try a fixed channel because I've heard that the auto-select causes some grief.
 
I haven't updated my OS since the last 10.6 came out, because there are no compelling new features they've added, but there have been compelling new bugs to be avoided.

Riiiiiigggghhht.

----------

Hopefully 10.11 will work with 'wifi'

Not touching yose***** again, staying firmly on mountain lions furry back

Mountain lion? The most cluttered and slow performing OS in recent years. At least get Mavericks

----------

OMG. My Magic mouse lag has finally gone when I'm using WiFi and have my power cable connected. I have been suffering with this for months!!!

Whole OS seems a lot smoother actually.

Now if I can only figure out what's causing the 20 second long gray screen before the Apple logo appears on startup I'll be satisfied.

A PRAM/NVRAM reset will fix the grey screen. For most people that started with 10.10.3
https://support.apple.com/en-gb/HT204063

----------

Hopefully. But the counting up started with OS X 10.7 or 10.8 for me.

See my comment above
 
Last edited:
I think it might have to do with the new GPL 3 bad license schemes.

Why would they replace mDNSResponder because of licensing reasons when the in the source code itself:

Code:
/* -*- Mode: C; tab-width: 4 -*-
 *
 * Copyright (c) 2012 Apple Computer, Inc. All rights reserved.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

It is licenced under the Apache licence. They replaced SAMBA with their own home grown solution because it moved to GPL3 but I doubt they would have kept using it because even under GPL they were limited to how much they could integrate Finder and SAMBA together (if SAMBA was LGPL then it would be a different thing entirely).
 
With the 5Ghz, do you specify a channel on the router or do you let it auto-select one? if you use automatic channel selection then try a fixed channel because I've heard that the auto-select causes some grief.

Tried channel auto and fixed, no difference.

Cisco though is using channel 160 and Airport - 44. I read somewhere that you need to use channel 54 and above to fix this issue.

Unfortunately you cannot set channel 160 for Airport...
 
Didn't encounter one single dropout after updating to the latest beta, says nothing yet though, on one of the last few beta's it stayed good for 1 week.
But, I think it solved it, about time Apple.
 
Tried channel auto and fixed, no difference.

Cisco though is using channel 160 and Airport - 44. I read somewhere that you need to use channel 54 and above to fix this issue.

Unfortunately you cannot set channel 160 for Airport...

Interesting, I just checked my router just then and my 5Ghz network is operating on Channel 36 (the router model is listed in the signature) and I'm not experiencing any issues for either my iMac or my MacBook Pro.

attachment.php
 

Attachments

  • Screen Shot 2015-05-31 at 12.41.41 am.png
    Screen Shot 2015-05-31 at 12.41.41 am.png
    49.3 KB · Views: 614
This is great news. My 2014 MB Air would take minutes to reconnect to wifi at work after I open the lid, and then when it did, 90% of the time it would slowing going to a halt and lock up forcing me to hold the power button to reboot. Or, it wouldn't even accept my login password... would just sit there at the login screen, waiting... and waiting... 10.10.4 fixes both these issues. Couldn't be happier with it!
 
This made a significant difference. I had been in the habit of waking my desktop up and going to make coffee while the network got re-established. Internet speed back to normal when browsing.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.