Safari DNS problem in Yosemite? Works, then slow death...

I honestly have no idea, lol!

Someone posted it somewhere around page 5 (I think) and they seemed to know what it means. I just tried it (because I had tried everything other option and nothing worked) and it worked (so far).

Though I did just come across a page 2 minutes ago that wouldn't load. But it wasn't Google, YouTube or Facebook which were the only sites I noticed having a problem with before.

jjabbb wrote:

…a page 2 minutes ago that wouldn't load. But it wasn't Google…

jjabbb, thanks!

To be clear, if I may, were/are you experiencing the same as I do with Google results, please; I haven't see that behaviour otherwise (widely) reported?

This just in:

http://9to5mac.com/2015/05/26/apple-drops-discoveryd-in-latest-os-x-beta-followi ng-months-of-complaints-about-network-issues-with-yosemite/

For those whom this is TL;DR:

After many complaints from the developer community about poor networking performance on Yosemite, the latest beta of OS X 10.10.4 has dropped discoveryd in favor of the old process used by previous versions of the Mac operating system. This should address many of the network stability issues introduced with Yosemite and its new networking stack.

...

Looking at Activity Monitor on OS X 10.10.4 seed 4, discoveryd is no longer loaded by the system — instead relying on mDNSResponder. The ‘new’ process is really the one Apple used to use pre-Yosemite and did not have these problems.

discoveryd gets handed its walking papers, and mDNSResponder gets called out of retirement.

Thats really interesting but I'm not clear what issues this will fix.

The problems I have experienced (in the order I noticed them) are:

1. Slow (or no) connection to WiFi when Macbook wakes up from sleep unless Bluetooth is disabled
2. Duplicate network names of devices on the LAN since I added an airport device. (also flakey Wake on LAN)
3. The WAN DNS lookup issue that this thread relates to.

These issues are all well documented in other threads

The latter issue does seem to have gone away since renaming the system configuration folder although I realise it didn't work for others.

is mDNSresponder implicated in all of these?

Peter

This can't come soon enough - thank you for sharing this, it gives me hope.

From what I've read and witnessed, all the networking issues, be they wifi, ethernet, failure to load images to emails, drop outs etc....are all relating to this flawed new part of the operating system 'discoveryd' that handles how Macs connect to websites.

By removing it and reverting to the old system 'mDNSresponder' we hope that the stability will be restored, which means I can get on with doing my work.

Fingers crossed.

The first issue that I mentioned was the slow connection to WiFi with bluetooth enabled. This problem first surfaced in the update to Mavericks and has continued with Yosemite. That makes me think it's not related to the other issues.

Fingers crossed though

drpeter, the only known 'solution' to addressing the actual cause of this issue (all other solutions address only the symptoms) was this:

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

For 12 years, the mDNSResponder service managed a surprisingly large part of our Mac's networking, and it managed this task well. But as of OS X 10.10, the mDNSResponder has been replaced with discoveryd, which does the same thing. Mostly.

I was never game enough to physically replace one piece of the core operating system with something else entirely (my Mac is for work).

However, this is exactly what Apple are planning to do with 10.10.4!

I think everyone who reported this problem via the official OS X Feedback form (myself included) deserves a round of applause.

I was fed up with this problem since last one year. I tried everything (change DNS.....and what not) No success. Last week wasted 3 hours with apple support and they made me to even format OS. Despite that nothing works....safari doesn't work.......i think best is to deactivate it and switch to chrome. The person on chat was trying to convince me that speed of safari is good, when i shown him chrome speed, he was so upset....

Also - decided not to buy any mac in future - windows is not good, but it doesn't give such basic fundamental problems....browser not working....****

I have a ticket open with Apple too - very helpful indeed.

Their engineers traced the problem to (Google) servers not responding to the packets which Safari on my machine is sending.

How to get Google to take notice?

Hi all,

I have read this thread because I have this problem but with a funny twist. I am currently writing this message in Chrome because my internet works and even Safari works with every web page but www.apple.com. What I think is amusing. !!!The only page I can't access is apple!!!!. 😁

Also I can't access other apple services so no iTunes store, or iBooks store, or updates (I think, at least I have not had one for ages).

I have tried all the suggestions here and none has worked for me.

It is a shame that the company that once was proud of producing the most reliable computers in the market has fallen into the trap of selling more and more without looking after quality and reliability.

They have created a name and they are now milking it. Sad!

Which ISP do you use; mine is AT&T. Could that be the common thread; throttling etc???

Hi all,

Please see this reply message.

I saw turning OCSP and CRL off and restricting connections for IP 91.121.43.224 under com.apple.WebKit.WebContent and com.apple.WebKit.Networking processes (it may be under any process but i saw it here), solved my HUGE bandwidth usage and also SLOOOOW Safari issues fixed both!!!

I started having the same problem again but this time, only with Facebook not loading. I hadn't changed anything since my last post (when everything was working fine) but I got a new iPhone and set up the iMessage.

I had turned on Bonjour in iMessage when setting it up with my new phone. I turned it off, restarted Safari and everything was back to perfect.

Thanks