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

That makes a difference! Renaming the proper folder worked for me, though I still have a DNS delay on safari.

Phew! Glad about that!

I am now half way through my fourth day with no DNS problems

The only problem I have found (and I don't know if it is related) is that a label printer wouldn't work and I had to reinstall it.

Had my first DNS timeout for the week – it's been about 4 days I think. It didn't last long, by the time I tested that DNS lookup worked on my phone and also via nslookup, Chrome had figured itself out.

thanks Carolyn.
your solution saved me! 🙂

I thought I was plain sailing with the systemconfig fix...despite having to do it every day. Yesterday for the first time in weeks I started up and it all worked. Today it didn't work and re-naming the config folder worked for 10 minurtes then failed. Looking inside the newly created SystemConfig folder I can see the 'discoveryd.BSP.plist' has not been re-created. A further re-boot and I have web browsing but it's quite slow.

This is a messy old business isn't it?

I have what may be a related problem: links on Google results pages almost always fail after a period of a minute or so with the error that the page cannot be found. A second click always goes right to the URL.

This seems to be more evident where Google constructs the link (on its results page(s)) as an argument after '?url=…' etc

Just had to share this - an entire morning wasted. I couldn't get the script to make a difference, and ended up renaming the systemconfig folder 6 times (and rebooting). You can imagine the profanities I was naming the folder by this stage.

I renewed the DHCP lease so much that I crashed the Airport Extreme. In the end I pulled the plug on the entire network, modem, router, switch, Mac the lot. Had a cup of tea and booted the whole lot up.

It is now working but I can't go on like this, I'm supposed to be running a business.

This OS is fundamentally flawed and I don't think Apple know how to fix it. I'm going to start badgering the media.

Having followed this thread for a while, I wanted to suggest something, and I apologize if it has been considered already.

For those of you who are having this issue, have you considered the possibility of a hardware problem? Yes, it seems like software/OS, but it's very possible that it's a hardware issue, maybe a flaky or intermittent one. You might want to take your machine in and have it looked at. Maybe replacing a network card, or something else, will help.

I bought an iMac 5K Retina a few months ago, and out of the box it acted very strangely -- something that seemed to be a software problem but clearly wasn't because it was a brand new machine. It took some convincing, because the problem was hard to reproduce in front of the service people, but I finally convinced them to replace the machine. The new iMac worked perfectly and I haven't looked back.

So, especially if you are under warranty, I'd bring it in and have it looked at. And, be persistent. Bring screen shots of the problem -- maybe even video -- in case they can't reproduce the problem at their location. This documentation is essential -- they can't just shrug their shoulders if you have pictures and video to show them of the problem. You may also want to consider bringing it to a local computer store that is Apple-authorized, particularly if you don't have luck with the "Geniuses". In the few times that I've had hardware problems in my 20+ years of owning Macs, it was the local store that went to bat for me with Apple and not the Apple Store.

What a terrible experience. I wish you luck with the media.

Unfortunately I think the problem is

1. It only affects a small number of users
2. It affects different users in different ways

I therefore think Apple will not worry unduly about a few unfortunates. It would be interesting to know how often this occurs on new machines (like mine) because if a substantial number of people started claiming that the machine was not fir for purpose and asked for their money back Apple may start taking it seriously.

I seem to be lucky that the problem is solved for me. (for now!)

I had a faulty iMac on delivery. This one is the replacement :-(

This was my working theory -

I had a mobileme account before everyhting switched to iCloud. I've had this MobileMe account for roughly 7 years, so my sync services are carrying over my keychains, bookmarks, notes etc ...

My phone, my laptop and my Mac Pro would randomly go into this DNS lag where I'd either have to reset my WIFI (airport) on the device having issue or reboot. Other machines in the house not tied to my iCloud account were fine.

When I upgraded to the iPhone 6 last week, I decided to let my old MobileMe turned iCloud account go. Made the appropriate photo/notes backup and rolled over to my Apple ID I orginally set up for iTunes and develpement. I switched over on all my machines and for the last week I have not had an issue.

Again - this was just a working theory, but I know iCloud seems to sync networks you've connected to in the past, and after 7 years I can't imagine that list looked that great between all the airports, hotels, diners, and coffeeshops etc ...

Either way I'm going to keep an eye on it going forward.

Thanks very much to those who have tried to shed light on my particular set of circumstances (Google constructed links (= www.google.com?url=***) failing the first time and working immediately afterwards.

I've got a brand new system which is working well in every other way.

I've restarted my Airport Extreme, repaired permissions, checked the cabling etc. I don't think it's hardware; if it were, then no other browser would work under these circumstances either.

I've tried a variety of other DNS settings.

It seems to be Safari 8 in 10.10 unable to know how to deal with Google's 'constructed' links, thus:

For https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0CCoQFjAB&ur l=http%3A%2F%2Fwww.nts.org.uk%2Fculloden… I get:

the first time. Reload the page and it loads perfectly!

!!!

The other clue against it being a hardware problem is that direct IP address connection always works fine.

I have a couple of bookmarks set up that point direct to the webpage IP address rather than the Domain Name. When I had lockup previously these bookmarks always connected immediately.

Don't remember who posted this solution and then this image, but this is what worked for me. I was having the same problem with images in Facebook, google images and YouTube. Also the same link problem someone just mentioned with google searches.

Three days now (knocking wood) and still working fine.

*Edit - I'm using ethernet, not wifi

jjabb,

What does 'Link-local only' (as opposed to 'Automatic') mean/do/imply, please?

Why would that work better?

Thanks!