1

We have Wi-Fi internet in our home which we access from at least five different devices (2 PCs, 2 phones, 1 Mac). On four of the five, the internet behaves perfectly fast enough, but on the six-month-old MacBook Air, the internet appears subject to intermittent delays (up to multiple minutes) loading a wide variety of web pages (on both Chrome and Safari). The Mac is performing all non-internet related tasks perfectly quickly. Strangely, when doing a speed test (speedtest.net) the performance on the Mac appeared to be the same as on the other devices (5mbps down/3mbps up).

I have no idea where to go from here.

EDIT: I am a long time PC user but my mac knowledge is very limited.

3
  • 2
    Next time it happens, see if it's due to DNS lookups stalling in discoveryd by running sudo killall discoveryd (the system will automatically relaunch discoveryd).
    – Spiff
    May 4, 2015 at 20:23
  • How much RAM? I had a user basically cripple an i5 mini (2011) that had been fine on 2GB until he upgraded to 10.10 and it became a sluggish lump of useless until it was fed a great deal more RAM.
    – Ecnerwal
    May 5, 2015 at 2:23
  • I would also gander a guess and say that it is DNS related. How long does it take when you run "dig A siteyouaretryingtoaccess.com" from the terminal?
    – deanvz
    Jun 24, 2015 at 13:23

3 Answers 3

2

Your problem sounds like DNS lookup stalls, and the new discoveryd daemon that was in OS X Yosemite (OS X v10.10.x) was the source of a lot of these problems.

The Yosemite update to v10.10.4 came out today (Tuesday 2015-06-30), and it replaces discoveryd with an updated version of the more mature and better-debugged mDNSResponder.

For most Yosemite users experiencing DNS stalls, the right answer is to install the 10.10.4 update now that it's out, rather than going through all the hassle of manually replacing discoveryd with Mavericks' (OS X v10.9.x's) old version of mDNSResponder.

Edit/Update: 10.10.4 is out now.

2
+25

See Ars: Why DNS in OS X 10.10 is broken, and what you can do to fix it

Random failures to resolve DNS names. This is rare, but every once in a while, Safari stops loading any and all websites. Turns out that the OS X DNS resolver has stopped working. (Command line tools such as nslookup, host, or dig still work because those use their own DNS lookup code.)

Copied from the Ars article...

Restoring mDNSResponder, if you dare

First a word of warning: if something goes wrong, your Mac may not be able to boot. This can be fixed by booting in single user mode and re-enabling discoveryd (see below). Be sure you have a recent backup just in case, and only follow the steps below if you are prepared to boot into single user mode if needed.

The first thing you need to do is find copies of 10.9 mDNSResponder, mDNSResponderHelper, and their plist files. On a 10.9 system, they're found in /usr/sbin/ and /System/Library/LaunchDaemons, respectively. These Terminal commands will copy them to the desktop for easy copying to the 10.10 system on which you want to install them:

cd ~/Desktop/
cp /usr/sbin/mDNSResponder .
cp /usr/sbin/mDNSResponderHelper .
cp /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist .
cp /System/Library/LaunchDaemons/com.apple.mDNSResponderHelper.plist .

Another way to get the mDNSResponder and its helper is from a Time Machine backup. Connect your Time Machine drive or click on the backup image on your (Time Capsule) network drive. Next, navigate to a backup from before October 16, when you were still running OS X 10.9, along these lines:

cd /Volumes/Time Machine Backups/Backups.backupdb/
cd <my machine name>
ls
cd <date/time of backup>
cd Macintosh\ HD
cp usr/sbin/mDNSResponder ~/Desktop/
cp usr/sbin/mDNSResponderHelper ~/Desktop/
cp System/Library/LaunchDaemons/com.apple.mDNSResponder.plist ~/Desktop/
cp System/Library/LaunchDaemons/com.apple.mDNSResponderHelper.plist ~/Desktop/

With these preparations in place, you can copy the mDNSResponder and helper to the OS X 10.10 machine:

sudo cp mDNSResponder /usr/sbin/
sudo cp mDNSResponderHelper /usr/sbin/
sudo cp com.apple.mDNSResponder.plist /System/Library/LaunchDaemons/
sudo cp com.apple.mDNSResponderHelper.plist /System/Library/LaunchDaemons/

Then, deactivate discoveryd and activate mDNSResponder. Remember, sudo makes a command execute with root or system administrator privileges, so it asks for a system administrator password. Don’t worry if you get "Could not find specified service."

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd_helper.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponderHelper.plist

Now reboot.

Should you wish to reactivate discoveryd, use the following commands. If your machine won't boot properly, boot in single user mode by rebooting while holding command-S and then you'll be able to type these commands. Type "exit" when you're done.

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponderHelper.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd_helper.plist

You may be wondering which new OS X 10.10 features no longer work because you're using an older version of such an important system component. As far as we've been able to tell in a short period of testing, all the headline ones all still there—Handoff and AirDrop work in both directions. Enjoy your rediscovered network stability.

  • No guarantees!
  • Find someone to help if you're not up to this.
  • Make a backup first.
  • Make sure you know how to boot into single user mode in case this doesn't work.
3
  • 2
    I can't believe it ... A modern OS needs to be fixed with such statements ? Are we stuck in the 1990's ?
    – user286640
    Jun 26, 2015 at 19:26
  • Not the 90s. These commands are from the 60s... ;-) We probably have to wait for 10.10.4 to get this fixed by a system update.
    – SPRBRN
    Jun 27, 2015 at 20:30
  • Software at times can by mistake have bugs placed back into it. This is how most of the SSL bugs that have existed have made it into stable SSL code repositories including Apple's. It even happens to Microsoft at times, they have released multiple updates, that basically fix the same problem but are released years apart.
    – Ramhound
    Jun 30, 2015 at 18:23
1

This may be totally useless since but since I cannot comment at this stage this comment is formed as an answer.

I recently had a similar issue with an older macbook pro and was tearing my hair out to figure it out. It was the thunderbolt bus/adapters/monitors etc interfering with the wifi...

So if you are using anything thunderbolt related I would suggest changing your wifi channel on your router(channel 1 worked for me).

HTH

1
  • This is more suitable for a comment than a true answer. Please refrain from this until your reputation allows you to post comments, thank you. Jun 27, 2015 at 16:03

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .