-
All replies
-
Helpful answers
-
Oct 23, 2014 4:39 AM in response to narribriby wparsons,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.
-
Oct 23, 2014 4:40 AM in response to shin727by pwinkeler,Experiencing the same types of problems and it is definitely not a Safari or Web problem. When this happens, evening trying to "ping" the unresponsive site fails because the name of the site cannot be translated into its corresponding IP address - the basic function of DNS.
However, when you use the "nslookup" tool you'll find that the DNS server your Mac is using at that time is perfectly happy to perform this translation!
What all that tells me is that Maverick's internal DNS caching is having trouble. This mechanism tries to cut down on the number of DNS translation requests by remembering the answers from before. In this case that mechanism appears to get stuck. I am going to try and figure which processes embody this mechanism to see if there is a way to unstick them
-
Oct 24, 2014 7:42 AM in response to pwinkelerby Moondragon85,I have/had exactly the same problem. 2013 iMac with Yosemity (10.10).
I think pwinkeler is right. The problem is systemwide but without affecting Google Chrome and the nslookup command.
Oddly enough – while writing this text – it just started to work again. So it doesn't seem to be permanent. But hopefully it gets fixed soon nevertheless.
-
Oct 24, 2014 10:55 AM in response to Moondragon85by gregfromsaint-lazare,I have been experiencing this problem as well. It is not just Safari. For example, when the problem happens, ping, telnet no longer work either yet nslookup will happily resolve the address I am looking for.
-
Oct 24, 2014 11:52 AM in response to gregfromsaint-lazareby Staley009,Same here, mid-2011 27" iMac. Odd though that Safari and Firefox have the problem but Chrome works fine. Obviously a Yosemite issue. Never had that problem until the update yesterday.
-
Oct 24, 2014 1:24 PM in response to Staley009by pwinkeler,Perhaps Chrome has its own DNS resolver stack and doesn't use the native one? A bit odd that would be though since Chrome does obey OS X' native proxy settings...
-
Oct 24, 2014 1:32 PM in response to pwinkelerby wparsons,I don't think it's related to Chrome at all... I get the exact same behaviour in Chrome, Firefox, Safari, ping, etc. Anything that needs a DNS lookup to resolve the host fails intermittently.
-
Oct 24, 2014 2:23 PM in response to narribriby MilitaryHealth,Thanks for sharing your info from apple support! It has been maddening, especially when you're trying to get work done!!!
I've done all the things mentioned (except trashing the cache file, which I'll try now...), and it sooo slooow.
When I was using the Yosmite beta version ... I don't recall that Safari was this slow!
Hopefully they get a fix for this soon!
-
Oct 25, 2014 1:14 AM in response to shin727by Erik Testmann,Same here. I have it on my MB Air (brand new), my old MB Air (4,1) and my iMac. Supports suggestion that you should change your DNS is crap. I have the problem at home where I use public DNS and in the office where we have our own DNS. If I set up a static DNS, I will not be able to access our
domain. My Windows machines and units still running Maverick do not have that problem.
When I use Chrome and Firefox, it works all the time, so it is definitely a Safari bug.
-
Oct 25, 2014 9:29 AM in response to MCW55by Phillip Howe1,I wiped my second disk and installed only Yosemite. At first I didn't even use my Apple ID on the confiruration. I have been on Facebook, Google Plus, Hulu. All the sites I was having issues with. NSLookup from command line works. Telnet works. I assume that when I upgraded and moved my apps and files over through the Mac Migration that something broke.
I don't know what it is. But there is a large amount of people who are having this same problem. At least I know a completely clean install Yosemite works properly.
-
Oct 25, 2014 11:03 AM in response to Phillip Howe1by DJ Bradshaw,The answer is that this is caused by the discoveryd process being crashed by an application on your system. Restart it with.
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plistYou will need to do this every time it stops working, a more long term solution is to find out what application is causing the problem and then disable Bonjour networking in it.
See these posts for more info.
http://apple.stackexchange.com/questions/151842/yosemite-cannot-resolve-domain-n ames
https://trac.adium.im/ticket/16827
It's disappointing that Apple's tech support gave up, rather than fixing the issue.
-
Oct 25, 2014 1:22 PM in response to MCW55by fauzzo,I have similar issues here, I have restricted my variables to this:
- my Internet connection: I have not the problem, or much less, If I use a different connection, for example iPhone hotspot;
- I don't have any issue on https sites, I do have issues with http sites in forms/logins submission only;
- the same issue happens on Yosemite/Safari 8 but even on iOS 8.1 on iphone and ipad when using my home wifi network;
- it happens for the domains hosted on one remote server only;
Chrome and Firefox are working without problems.
I have made a fresh installation of Yosemite and then I have imported user data from TimeMachine backup.
Hope a fix will come soon!
-
Oct 26, 2014 3:37 AM in response to MCW55by narribri,I took the fairly drastic step of a complete disk erase and reinstall this morning (Desperate! My business depends on my computer) and it seems to have worked. Everything's running well, performance is back to normal and browsing is perfect on secure and unsecured sites. I'm very carefully reinstalling software and backing up between each install, but all my basics are on and everything is fine. If you've got good backups (not time machine) then this might be an alternative to waiting for apple.
-
Oct 26, 2014 3:25 PM in response to MCW55by -mbk,Add me to the list. DNS lookups fail in Safari, Chrome, and even ping. I can ping an ip address, but any DNS lookup fails. Other machines on the same network work just fine, so it isn't my router setup.
-
Oct 27, 2014 1:19 AM in response to -mbkby htmanning,I'm having this same issue too. Safari works, then slows dramatically. Open Chrome, good to go. The problem is Chrome is slow and jerky on Yosemite compared to Safari (when it's working right).
Boy this software is buggy.