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 6 of 17 last Next
  • by Daniel Burkland,

    Daniel Burkland Daniel Burkland Nov 19, 2014 12:09 PM in response to EYing
    Level 1 (15 points)
    Nov 19, 2014 12:09 PM in response to EYing

    Hitting this issue everyday and none of the suggested solutions have resolved this issue (running 10.10.1). Apple needs to fix this as this is a show stopper if one wants to ever be productive with Safari...

  • by ascanio,

    ascanio ascanio Nov 22, 2014 8:17 AM in response to MCW55
    Level 1 (13 points)
    Mac OS X
    Nov 22, 2014 8:17 AM in response to MCW55

    Same problem here. Retina 13" first gen, 10.10.1... and Safari times out on famous sites (eg.: citymapper). Chrome does the same. I wonder if it is an OS problem, since it happens with more than one browser. I had issues on 10.10, but they got even worse on 10.10.1. Apple, please, increase your quality controls on software, it's been a few years you're coming out with buggy stuff. Are you aiming to become the new Microsoft?

     

    I deeply hope 10.10.2 will solve it.

  • by puzne,

    puzne puzne Nov 24, 2014 2:00 AM in response to ascanio
    Level 1 (0 points)
    Nov 24, 2014 2:00 AM in response to ascanio

    not all posts here are of same problem. In some cases (mine included) chrome continues to work well while safari seems as if it can't reach the interweb. This happens to me when my comp comes out of sleep. Recycling wifi off and wifi on again resolves the problem until next time.

  • by Lexiepex,

    Lexiepex Lexiepex Nov 24, 2014 2:16 AM in response to MCW55
    Level 6 (10,519 points)
    Mac OS X
    Nov 24, 2014 2:16 AM in response to MCW55

    Nobody tried this??? :

    Flush the DNS cache:

    in Yosemite (not the older OSX):

    Open Terminal (in Utilities folder),

    copy paste following command into Terminal

    sudo discoveryutil mdnsflushcache;sudo discoveryutil udnsflushcaches;say flushed

    and hit enter,

    Quit Terminal

    this should help immediately.

    in older OSX:

    dscacheutil -flushcache

    Lex

  • by ascanio,

    ascanio ascanio Nov 24, 2014 5:17 AM in response to Lexiepex
    Level 1 (13 points)
    Mac OS X
    Nov 24, 2014 5:17 AM in response to Lexiepex

    No change, at least to me...

  • by CoronaX,

    CoronaX CoronaX Nov 24, 2014 8:57 AM in response to puzne
    Level 1 (4 points)
    Nov 24, 2014 8:57 AM in response to puzne

    Exactly same issue an latest update didn't fix anything.


    When I started linking Safari over chrome all these issues..Ugghhh!


    Apple are you reading this???

  • by MisterMojo,

    MisterMojo MisterMojo Nov 24, 2014 12:00 PM in response to CoronaX
    Level 1 (0 points)
    Nov 24, 2014 12:00 PM in response to CoronaX

    Since I haven't upgraded to iOS 8 I'm not affected but I am monitoring this thread so I will know when it is safe to upgrade...

     

    My question: Are Apple Airport Extreme Base Stations (not the latest version...) susceptible or is the problem primarily with third-party routers? I  don't recall seeing any mention of the AEBS but I could have missed it... I wouldn't upgrade to Yosemite/iOS8 even if Apple routers are immune but I am curious. If AEBS are usually not affected it could be a clue as to the cause of the WiFi problems.

  • by james_dh,

    james_dh james_dh Nov 24, 2014 7:46 PM in response to MCW55
    Level 1 (0 points)
    Nov 24, 2014 7:46 PM in response to MCW55

    This isn't an iOS 8 problem. This isn't a router problem. It's not a problem with Safari crashing immediately upon startup. It's a Safari 8 DNS problem in Yosemite (as the original discussion title suggests).

     


    How is this most easily observed? I'd say when trying to browse to a website w/ Safari and getting a "Site Not Found" error, yet you are able to visit the site in Chrome/Firefox just fine.

     


    Too many people on here are posting unrelated problems and it's detracting from the OP's discussion. Granted, this is pretty much the life story of Apple's discussion forums, but for the sake of everyone on here who is suffering from the ORIGINAL problem, please read a bit before posting every problem under the sun that you think is related.

  • by puzne,

    puzne puzne Nov 24, 2014 11:39 PM in response to puzne
    Level 1 (0 points)
    Nov 24, 2014 11:39 PM in response to puzne

    I have this problem with an airport extreme. I'd say it's about 5 years old (the extreme).

  • by Jonathan Laliberte,

    Jonathan Laliberte Jonathan Laliberte Nov 26, 2014 11:17 AM in response to james_dh
    Level 1 (59 points)
    Apple TV
    Nov 26, 2014 11:17 AM in response to james_dh

    Having this same problem. Yosemite 10.10.1. Retina iMac.

    I've tried: clearing caches, clearing dns cache, disabling/deleting ipv6 addresses. Nothing helps

    For me it's happening with one specific site right now, and sometimes only on https. If I open the page in Chrome it works without a problem.

  • by FJ9999,

    FJ9999 FJ9999 Nov 27, 2014 7:05 PM in response to MCW55
    Level 1 (1 points)
    Nov 27, 2014 7:05 PM in response to MCW55

    After trying everything and nothing worked, I went into System Preferences > Network > [ServiceName] > Advanced > DNS and changed my DNS servers from the Google DNS servers:

     

    8.8.8.8

    8.8.8.4

     

    to the Open DNS servers:

     

    208.67.222.220

    208.67.222.222

     

    This immediately fixed the problem that I was having for a week, which was that craigslist.org was inaccessible on my Mac (same problem on all browsers: Safari, Chrome, Firefox).

     

    I don't know if this will fix all of my problems, but it clearly fixed this one.  I had been using Google DNS servers for years with little problem, but something went awry.  Seems to be related to Yosemite, but can't swear to it.

  • by Lexiepex,

    Lexiepex Lexiepex Nov 28, 2014 12:33 AM in response to FJ9999
    Level 6 (10,519 points)
    Mac OS X
    Nov 28, 2014 12:33 AM in response to FJ9999

    This is depending on where you are: in Europe in general the OpenDNS you recommend are better, in USA in general GoogleDNS does better.

    You have only one to put in, so why not take one of each !

    There is a tool called Namebench that can suggest the best for your region by measuring all servers including the regional ones. Then it comes up with a suggestion of 3 DNS. Although if you run Namebench 2 times on one day, it often finds a different set (it takes in count the real throughput).

  • by reggie_g,

    reggie_g reggie_g Nov 28, 2014 10:30 PM in response to ron2you
    Level 1 (0 points)
    Nov 28, 2014 10:30 PM in response to ron2you

    Worked for me!  Thank you.

  • by Vicky MBA 11" Mid 2011,

    Vicky MBA 11" Mid 2011 Vicky MBA 11" Mid 2011 Nov 29, 2014 1:02 AM in response to Carolyn Samit
    Level 1 (0 points)
    Nov 29, 2014 1:02 AM in response to Carolyn Samit

    Hi Carolyn,

    i did all you advised here and it didn't work for me. then i went to preferences -> network -> advanced -> proxies. there was a box "auto proxy discovery" ticked so i clean it, "the use passive ftp mode box" i left ticked,  i didn't touch any other settings in network preferences and Safari is now working perfectly. i had problem with open anything on safari since installing Yosemite, only chrome and firefox worked. I don't know if i did the right think with proxy but my Safari is back thanks a lot. Rgds/W

  • by Moosemanusa,

    Moosemanusa Moosemanusa Nov 29, 2014 4:43 PM in response to Vicky MBA 11" Mid 2011
    Level 1 (0 points)
    Nov 29, 2014 4:43 PM in response to Vicky MBA 11" Mid 2011

    using  MCP Retina Mid 2012 model

     

    Yosemite

     

    Safari / Chrome / Firefox - All slow lookup's on DNS (30 seconds avg)  - Appears to popular sites - Facebook / Youtube / Other Google Products!

     

    Amazon is fine!

     

    Tried different DNS / Old mac use to use Mavericks, no problems, upgraded to Yosemite now it has the same problem.

     

    sudo discoveryutil mdnsflushcache;sudo discoveryutil udnsflushcaches;say flushed


    Is working for the moment, its a DNS stack issue for sure.

first Previous Page 6 of 17 last Next