Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

BrianGilbert

macrumors newbie
Original poster
Jan 31, 2015
3
0
I’m a web developer and I use my MBP as a local development environment, one of the changes in Yosemite has made that not really work when I’m somewhere that I don’t have an Internet connection.

I run a local DNS server so that I can wildcard a certain top level domain to always resolve to localhost, but as of 10.10 there are no resolvers available when you are disconnected from all networks, so now if I’m somewhere without an Internet connection I have to tether to my phone just to access local development sites :(

I’ve contacted Applecare and the supposed response from the engineers was “thats expected behaviour”, the applecare contact I had even used the word feature, while at the same time acknowledging that it’s unfortunate.

Here is a Video that compares 10.9 and 10.10 behavior:
https://www.youtube.com/watch?v=3m9OI_AjCx8

Looking for workarounds or to help get some more visibility of this issue so that Apple might address it sooner rather than later.

Cheers
Brian
 
Apple is using a new (incredibly buggy) DNS resolver for Yosemite. It's also why you've seen a plethora of computer names with a (2) after it, because the DNS resolver crashes....

I've heard of people replacing the DNS resolver from 10.10 with the one in 10.9, you could try that. Sorry I don't have any specific instructions for it.
 
I run a local DNS server so that I can wildcard a certain top level domain to always resolve to localhost, but as of 10.10 there are no resolvers available when you are disconnected from all networks, so now if I’m somewhere without an Internet connection I have to tether to my phone just to access local development sites :(

Just use /etc/hosts in some way.

If you can't be bothered using terminal you can just do it through a prefpane:
http://osxdaily.com/2012/07/30/easily-edit-hosts-file-in-mac-os-x-from-a-preference-pane/

Or Gasmask:
http://www.clockwise.ee/gasmask/
 

This does indeed resolve the issue, but in the words of applecare liaison, who knows when that will stop working..

----------

Just use /etc/hosts in some way.

If you can't be bothered using terminal you can just do it through a prefpane:
http://osxdaily.com/2012/07/30/easily-edit-hosts-file-in-mac-os-x-from-a-preference-pane/

Or Gasmask:
http://www.clockwise.ee/gasmask/

That would be ok if I didn't spin sites up all the time.. this is why I use a wildcard DNS entry to start with.., thanks for trying to be helpful tho.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.