MCW55

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

Safari 8.0 + Yosemite seems to have a problem. It will work for a while, then begins to fail to load and is unable to resolve top level domains -  "Safari Can't Find the Server ... [e.g. apple.com]"

 

Restarting Safari often resolves the issue for a while (minutes, hours?), then performance deteriorates until it finally gives up and generates the error. Chrome, on the same machine, does not suffer this problem.

 

17" Intel iMac, Safari 8.0, Yosemite, Exede broadband (satellite).

 

Anybody else see this issue and/or have a solution?

 

iMac (27-inch Mid 2011), OS X Yosemite (10.10)

 

iMac (27-inch Mid 2011), OS X Yosemite (10.10)

Posted on Oct 21, 2014 1:44 PM

Close

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

  • All replies
  • Helpful answers

first Previous Page 8 of 17 last Next
  • by BobinStanmore,

    BobinStanmore BobinStanmore Dec 7, 2014 7:11 AM in response to MCW55
    Level 1 (5 points)
    Dec 7, 2014 7:11 AM in response to MCW55

    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.

  • by Chas21,

    Chas21 Chas21 Dec 7, 2014 7:19 AM in response to BobinStanmore
    Level 1 (4 points)
    Photos for Mac
    Dec 7, 2014 7:19 AM in response to BobinStanmore

    A very good post. Apple appear to adopt a "we cannot confirm or deny there is an issue" attitude that I find unacceptable. I suppose they have enough customers and money to treat concerns like us as they please. Poor business practice.

  • by cyvi937,

    cyvi937 cyvi937 Dec 7, 2014 8:18 AM in response to MCW55
    Level 1 (100 points)
    Dec 7, 2014 8:18 AM in response to MCW55

    Try this:

     

    1. Open System Preferences.
    2. Click on Network.
    3. Remove all of the services in the left-hand pane (Ethernet, Wi-Fi, etc.) using the minus symbol.
    4. Click Apply and close System Preferences.
    5. Reopen System Preferences.
    6. Add back in the service(s) you want using the plus symbol.

     

    This seems to have worked for the network problems I was experiencing (which were intermittent, system-wide and not limited to Safari).

  • by MTPP,

    MTPP MTPP Dec 7, 2014 8:24 AM in response to BobinStanmore
    Level 1 (0 points)
    Dec 7, 2014 8:24 AM in response to BobinStanmore

    Pages don't load on any browser.

    I have read almost all the posts on this issue and find most of them to advanced for me (I'm new with MAC), so I can only agree with you.

    Apple SHOULD be doing something about it. Yosemite seemed good but it lasted a few weeks.

    I already have 10.10.1 and the problem is even worse.

    I need help please !!!

  • by Owein Mynydd,

    Owein Mynydd Owein Mynydd Dec 7, 2014 8:35 AM in response to cyvi937
    Level 1 (0 points)
    Dec 7, 2014 8:35 AM in response to cyvi937

    Thank you cyvi937.  This has resulted in enough improvement for me to try Safari as my default browser again for a while.

    I will report back (and change back to Firefox!) if my problems return.

  • by AirCordell,

    AirCordell AirCordell Dec 7, 2014 8:47 AM in response to Owein Mynydd
    Level 1 (0 points)
    Dec 7, 2014 8:47 AM in response to Owein Mynydd

    The worst part of this problem seems to be that for Mac users, the problem extends beyond Safari to other functionality that seems to rely on Safari performance.  Yesterday I reported that restarting my Mac cleared the problem for 6 days.  Today I woke up to find that the relief provided by yesterday's restart lasted less than one day.  Restart still seems to be the easiest way to go until Apple fixes the problem.

  • by Richard Blakemore,

    Richard Blakemore Richard Blakemore Dec 8, 2014 1:07 AM in response to cyvi937
    Level 1 (12 points)
    iPhone
    Dec 8, 2014 1:07 AM in response to cyvi937

    cyvi937

    I tried removing all network services, closing preferences and re-installing wifi and ethernet.  So far this works. Fingers crossed.  Other fixes have worked for a bit. Hope this one takes as my only option is to scrap Safari for Firefox.

     

    Thanks

  • by Unloadedone,

    Unloadedone Unloadedone Dec 8, 2014 6:32 AM in response to Richard Blakemore
    Level 1 (4 points)
    Dec 8, 2014 6:32 AM in response to Richard Blakemore

    OOkay this worked for me so far but it points to a bigger problem with Safari that needs to be addressed.

     

    Open system stem prefrences and select advanced > hardware.

     

    From rom the drop down menu slelct manually instead of automatic.

     

    Under MTU change the value from 1500 to 1400. Pages that are slow to resolve seem to load faster but I need more time to be sure.

     

    Why the default value of 1500 which was fine in Mavericks and prior systems updates needs to be altered baffles me but again pages are loading more quickly.

     

    Also lso of note on my system, popular pages that update frequently like news sites, send safari into super slow mode prior to this adjustment. It seems like there's a cache issue as well. What a mess.

  • by BobinStanmore,

    BobinStanmore BobinStanmore Dec 8, 2014 7:55 AM in response to MCW55
    Level 1 (5 points)
    Dec 8, 2014 7:55 AM in response to MCW55

    I have started a discussion on this issue on http://www.mac-forums.com under the title "Safari 8.0 running slow in Yosemite 10.10.1" to see if the users of that site can throw any further light on this subject.

  • by Richard Blakemore,

    Richard Blakemore Richard Blakemore Dec 9, 2014 12:12 AM in response to cyvi937
    Level 1 (12 points)
    iPhone
    Dec 9, 2014 12:12 AM in response to cyvi937

    cyvi: Your fix is still working after 24 hours.  Thanks again.

    Richard

  • by Moosemanusa,

    Moosemanusa Moosemanusa Dec 9, 2014 10:13 AM in response to Richard Blakemore
    Level 1 (0 points)
    Dec 9, 2014 10:13 AM in response to Richard Blakemore

    Reinstalled - Fresh Install of Yosemite! (Not a Time Machine but fresh)

    Removed Network Devices - Re-added

    Changed MTU to 1400

     

    No change, it comes and goes!

     

    Apple needs to take action as this is happening to a lot of people..

     

    The DNSFlush works somedays and not others.. My biggest problem is Google searches take 1 minute to complete, facebook doesnt work, youtube if I'm lucky.

  • by gottapulse,

    gottapulse gottapulse Dec 12, 2014 4:56 AM in response to MCW55
    Level 1 (8 points)
    Desktops
    Dec 12, 2014 4:56 AM in response to MCW55

    I have the same problem and i am not running Yosemite. A couple of days a go I used my wife's Macbook Pro and Safari was unusable. Did a reset, downloaded and installed CleanMyMac2 and ran it, ran Disk Utility and repair permissions. Didn't make any difference. Launched Firefox and browsed to same sites as I had tried with Safari with no problems. Just fired up my iMac, Safari exhibiting the same issue. Same with my Macbook Air. So the common denominator must be Safari. All my macs are running OSX 10.9.5

  • by Lexiepex,

    Lexiepex Lexiepex Dec 12, 2014 5:12 AM in response to gottapulse
    Level 6 (10,519 points)
    Mac OS X
    Dec 12, 2014 5:12 AM in response to gottapulse

    Better start a new thread and post the link here, explain the issue and tell that you use CleanMyMac, and send an Etrecheck list with it.

    Lex

  • by izzyisizzyaint,

    izzyisizzyaint izzyisizzyaint Dec 12, 2014 1:34 PM in response to Unloadedone
    Level 1 (8 points)
    Mac OS X
    Dec 12, 2014 1:34 PM in response to Unloadedone

    Unloadone's solution worked for me right away. I made the change to 1400 before upgrading to Safari 8.02. However, I did not test for worse performance by going back to 1500. Just too much to do.

    2014-12-12t13-15-57.jpg

     

    Might note that even before changes, Safari worked better in other accounts on my machine. The slowdown was occurring in my main account from which I do most of my browsing.

     

    Safari works just fine now.

     

    Thanks so much,

    gerry

  • by ascanio,

    ascanio ascanio Dec 13, 2014 8:52 AM in response to izzyisizzyaint
    Level 1 (13 points)
    Mac OS X
    Dec 13, 2014 8:52 AM in response to izzyisizzyaint

    unfortunately, even after having edited MTU size from 1500 to 1400, nothing changed. As soon as I restarted it seemed to work, but it took me a couple of reloads of the usual sites to start idling again on sites like:

     

    citymapper.com

    tfl.gov.uk

    even logging back to this discussion was impossible. I had to use Chrome again.

     

    I was hoping Safari 8.0.2 would have solved it, but it seems Apple doesn't want to acknowledge the problem.

     

    Can we do anything to stimulate them? I don't think they browse all the discussions, so it might be useful to organise a way to communicate with them. A petition? An e-mail to Tim? Submitting bugs to Apple has never helped, as far as my experience.

     

    @

first Previous Page 8 of 17 last Next