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

Im also having the same issue. Safari appears to work for a while then errors out or pages do not display. I also am running Yosemite on a 27" iMac (2011)

Same here on a 21 inch 2012 iMac. Fairfox and Chrome run perfectly.

Same happens to me with all browsers (Chrome, Safari) BUT when logged as secondary user (guest or another, not the administrator main account). iMac 21"

Seems to be something related to "secure connection" as the browser stops with that message...

My daughter is also seeing this issue in her MacBook Pro 13". She is getting rather frustrated over it

Hi ..

For, "can't connect to server" issues, Apple suggests using Open DNS or Google DNS > Safari 5.0.1 or later: Slow or partial webpage loading, or webpage cannot be found

For OpenDNS.

Open System Preferences > Network > Advanced > DNS

Click + and type:

208.67.222.222

Click + again and do the same.

208.67.220.220

Click OK.

Quit and relaunch Safari to test.

If that didn't help, back to the DNS tab. Select the 208 addresses then click ➖ under the DNS Servers panel to delete.

Then click + to add Googles.

8.8.8.8

and 8.8.4.4

Then click OK and try Safari.

Using icloud webmail services does not work after a while and CPU work load goes up to 100%.

Being behind a firewall I require a certain DNS.

This is very frustrating.

Currently I am using Firefox

Solutions?

I have been using Google DNS from the start. Still experiencing the same issues.

Facebook responds terribly in Safari and even Chrome.

Google+ I have difficulties with Chrome displaying images

Yep, same problem. I've been through heaps of troubleshooting with apple support, added those dns numbers mentioned in the thread and still nothing. Fresh reinstall of Yosemite x4, still nothing. This update is extremely annoying, everything was working fine with Mavericks and now my computer is basically crippled.

Hi Phillip...

I'm not having issues with Facebook on either Safari or Chrome running Yosemite. Try maintenance for Safari.

Might be a cookies, cache, or extensions, issue.

From your Safari menu bar click Safari > Preferences then select the Privacy tab.

Click: Remove All Website Data

Then delete the cache.

Open a Finder window. From the Finder menu bar click Go > Go to Folder

Type or copy paste the following

~/Library/Caches/com.apple.Safari/Cache.db

Click Go then move the Cache.db file to the Trash.

Quit and relaunch Safari to test.

If that doesn't help, troubleshoot Safari extensions.

From the Safari menu bar click Safari > Preferences then select the Extensions tab. Turn that OFF, quit and relaunch Safari to test.

If that helped, turn one extension on then quit and relaunch Safari to test until you find the incompatible extension then click uninstall.

If nothing above worked, restart your internet modem and router if you use one then try Facebook on Safari.

I've tried all those, it didn't do anything

I don't think it's a browser or extension issue at all.

I'm having the same issue intermittently, it happens only on new requests (an xcode update continued downloading while browsing went in and out half a dozen times). When it does happen, not even ping will resolve a host name. I've mainly use FF, but Chrome and Safari are both affected the same.

I agree with wparsons message above. When it happens the choice to Open Page With (another browser) is greyed out. I don't think it is user settings or extensions.

Just got off the phone with tech support, they've been through all the troubleshooting stuff. It's not a network or ISP issue, it doesn't appear to be a problem with the update or Safari. They've basically said be patient, its a new OS and things will work out in time.

I have the same issue. Macbook pro retina 13 (late 2012) with Yosemite and Safari 8.0

What I do is open the website on chrome and then come back to safari, refresh the page(open again)

and then safari connects to the website.

What a pile of nonsense from tech support, I didn't have a single issue until the update, and it most definitely isn't going to fix itself. Whatever the issue is, it's deep in the network stack for the OS. I'm going to plug mine into a wired connection to see if it happens then as well, or if it's isolated to wifi. I know it's not the router/wifi itself because no other devices have this issue, and existing downloads keep downloading even during the issue.

I've also read they replaced the DNS related code in the update (discoveryd replaced mdnsresponder), and since this appears to be 100% DNS related I would bet that the issue is with discoveryd.