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

It worked for me too (Macbook Pro (retina) mid 2013), but only after full restart. User log-out and back was not enough.

A restart works for me but after a bit, the problem resurfaces. This is an issue that may be deeply embedded in the inner workings of safari. Something is wrong and it's very frustrating. Chrome and Firefox don't have this issue for me but I prefer to use safari as my daily driver. But until an update fixes this, I'm afraid it's Firefox for me. But Apple, please fix this. Everyone, take a moment to send feedback to Apple. This is ridiculous.

Yes, I experience the same. The problem resurrects :-(. I hoped restarting was a Microsoft feature. I am astonished having to restart my macbook...

Hi Carolyn,

Something is serious wrong with the new version of Yosemite or Safari. Safari works after completely shutting down my MB Pro for the whole night. The next morning Safari works for an unpredictable time. At random Safari stalls and the blue progress bar stops at 20% loading a web page. Safari is unusable for the rest of the day. So Firefox is for me an alternative.

However your recommendations of the DNS settings to 8.8.8.8 and 8.8.4.4 seems to work.

Hurray!

Tnx, Hans

In Europe add these two also

208.67.222.220

208.67.222.222

I too have had to move over to Firefox, and I will stay there until Apple have come up with a reliable fix.

Apple had to have seen this before releasing Yosemite, and shouldn't have been so hasty.

It is supposed to be every company's role model but this was not good practice.

Owein Mynydd

Yeah, me too. I switched to Chrome as it has a better full screen management.

Facebook, Twitter and many other important websites (even logging back to this conversation took me minutes) load very slowly and often time out.

Not happening with Chrome or Firefox. APPLE WAKE UP!!!

Yosemite is the buggiest OS ever! And I have been a loyal Mac user since 1987, since System 6.

@

Amen to that..

The DNS bug appears to be resolved flushing the DNS cache.

Still no idea why they had users auto logout after 60 minutes turn on after the upgrade is beyond me..

System - Security and advance turns that off.. Bugged me for weeks..

Wifi is unstable still also!

This is why I moved from my Iphone to the other guys.. I was tired of the buggy software.. Now my MBP is the same!

I thought that Safari did not stall any longer by adding DNS numbers

8.8.8.8

8.8.4.4

208.67.222.220

208.67.222.220

But the problem showed up this evening again. I will be switching over to Firefox.

Safari does not work properly!!!

Sorry to say.

Hans

Hans wrote:

I thought that Safari did not stall any longer by adding DNS numbers

8.8.8.8

8.8.4.4

208.67.222.220

208.67.222.220

But the problem showed up this evening again. I will be switching over to Firefox.

Safari does not work properly!!!

Sorry to say.

Hans

I have tried OpenDNS, Google DNS, Open NIC, my ISP DNS both locally and through my router to no avail. Safari doesn't care what you have entered, it just slows down again.

Confirming what others have said, including in 10.1.1:

1) Safari, iTunes Store, and App Store access all go out at the same time. Firefox, Thunderbird, and Chrome all work fine.

2) In Safari, progress bar goes about 1/8 of the way across then stops.

3) Restarting solves the problem until it eventually occurs again (after a few sleep/wake cycles)

4) Switching DNS to 3rd-party servers works immediately (Safari, iTunes Store, and App Store immediately load without my having to do anything directly to them) but temporarily (through a few sleep/wake cycles) then it eventually occurs again

Just on a hunch, when #4 eventually failed, I went back to my provider's DNS server and Safari, iTunes Store, and App Store all connected again immediately without my having to do anything directly to them.

So it appears to be that changing the DNS server clears the problem, then when the problem occurs again you can go back to your original server. That said, I can't promise that there wasn't a restart in there somewhere after I made the original DNS switch.

I didn't try the sudo suggestion as I am logged in as a non-admin so it doesn't recognize my password as authorized for sudo.

Same here Yosemite 10.10.1 and Safari 8.0. Just started having the problem where Safari can't find the server. Maybe it should look harder? I'm going to try all the suggestions and find out what works and give feedback as appropriate. Thanks to all of you who are far more knowledgeable than me and have come up with potential fixes. BTW, Chrome is fine, but I have all my bookmarks and reading lists on Safari so that's what I want to work.

I too am having the same troubles. I have tried all fixes stated in the thread. Things have gotten a little better after the suggested fixes but part of the problem continue to exist.

I can keep Safari alive and running for the most part. But I can make it fail very regularly. If I attempt to download one file, Safari will stay alive 99% of the time. If I up the download cue to 2, it seems to work 99% of the time. If I try to download 4 or more MP4 or FLV files via Safari at the same time it seems to fail within a minute.

I have tried downloading from different servers with different results. That is to say if I try to download 5 400+ megabyte MP3 files from my personal server at 1&1 it seems to work every time. However most sites that use tokens in their paths will fail 100% of the time when I download more then 4 MP4 or FLV files.

Once the download fails, there is no way to resume it. Canceling and restarting the download again results in Safari failing. If you attempt to load any page after the fail you get the blue progress bar loading 1/4 of the way and the whole thing hangs. If you then quit Safari and restart it and attempt to restart the download it will hang again. BUT if you quit the browser and throw the half downloaded temp files into the trash and empty the trash, then restart Safari and restart the download it will start over and work as long as you only try to download only TWO of the files. If you try to download FOUR or more it fails again.

So I am able to limp along downloading only two things at a time.

I also noticed that the date on the temp containers that contain the partial download and the Info.plist is "January 24 1984". I think the date thing is a small secondary bug.

It just seems that when I download more then 4 MP4 or FLV files at the same time from a large collection of sites Safari fails.

Let's all hope this gets figured out soon.

Simple restarting my Mac temporarily "fixed" the problem...for 5 days. Just restarted again.

We have three Macs (MBPro (15", Late Mid 2009, 2.53GHz Core 2 Duo with 8GB RAM); IMac (27", Late 2009, 2.66 GHz Core I5 with 16GB RAM); and MBAir (13", Mid 2013, 1.3 GHz Core I5 with 4GB RAM)) which are demonstrating browsing issues with Safari 8.0 on Yosemite 10.10.1. The interesting point is that the three machines cover a range of performance and capacity short of latest retina displays. All worked fine on Mavericks, Mountain Lion and earlier iterations of OSX. Crome seems to work OK but Safari is what we are used to, so ideally we want to stick with the devil we know.

The numerous suggestions above seem to work for some but not others. I have tried some (e.g. cleaning cache which didn't work while I still have fingers crossed to see if shutting down IPv6 has worked).

But, the point of this posting is to recognise, as many of you have in your posts above, that there is a problem with Safari 8.0 which Apple needs to address in order to keep its users happy. I am sure it does not want everyone to give up on Safari and run to rival Google's Crome or to Firefox. I have seen NO acknowledgement from Apple that they recognise there is an issue for resolution. That being the case, how do we bring this to their attention? Is there a moderator to this site who can acknowledge that Apple is looking to resolve the problem? Are there other means of getting a response from Cupertino?

Thoughts on how to get the issue acknowledged by Apple would be appreciated. At least we then have the hope it will be resolved in the hopefully not too distant future. Sorry for being long-winded.