Closed mjroeleveld closed 8 years ago
^ this fixed it for me
Thanks, did it for me as well.
I ran the script after this commit and still have this problem.
Looks like this is due to a change in Yosemite, I can confirm it's happening again..
10007 > scutil --dns
DNS configuration
resolver #1
nameserver[0] : 192.168.0.1
if_index : 4 (en3)
flags : Request A records
reach : Reachable,Directly Reachable Address
resolver #2
domain : ld
nameserver[0] : 127.0.0.1
flags : Request A records, Request AAAA records
reach : Reachable,Local Address
DNS configuration (for scoped queries)
resolver #1
nameserver[0] : 192.168.0.1
if_index : 4 (en3)
flags : Scoped, Request A records
reach : Reachable,Directly Reachable Address
[/etc/resolver]
[brian]
10008 > scutil --dns
No DNS configuration available
When connected to network:
10008 > dns-sd -G v4 aegir.ld
DATE: ---Wed 10 Dec 2014---
13:57:45.011 ...STARTING...
Timestamp A/R Flags if Hostname Address TTL
13:57:45.012 Add 2 0 aegir.ld. 127.0.0.1 15
When disconnected
10009 > dns-sd -G v4 aegir.ld
DATE: ---Wed 10 Dec 2014---
13:57:56.497 ...STARTING...
Timestamp A/R Flags if Hostname Address TTL
13:57:56.498 Add 2 0 aegir.ld. 0.0.0.0 60 No Such Record
It looks like there won't be a quick fix for this.. multiple reports of this problem on the interwebs as of Yosemite
Supposed workaround: Enable your Ad-Hoc Wifi Network. (though it only appeared to allow terminal based DNS stuff, not browser)
That's confirmed. Browser definitely doesn't work. I have to do a lot of my work offline so I'm kind of stuck at the moment. I may have to have MAMP configure the sites off the same codebase for offline use.
@brentratliff you can always add a manual entry to /etc/hosts , that at least stops you from having to install another full stack.. I have a meeting with apple genius next weekend to see if this can get resolved.
you could also try this.. https://github.com/joedj/yosemite_dnsfix (didn't appear to work for me though)
I have been adding them in /etc/hosts. I meant to post that here for others. It wasn't working the first time I added them, so I looked into MAMP, but worked after a reboot.
@brentratliff to flush your local DNS execute the following (so you don't need to reboot when adding new host file entries)
sudo discoveryutil mdnsflushcache;sudo discoveryutil udnsflushcaches
This has been escalated to Apple engineers by myself and I am awaiting a response, a workaround that I've confirmed works (but am not electing to use myself) is available at: http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-you-can-do-to-fix-it
Hmm, I don't think I want to take that risk either. Did you get a response?
Still awaiting a response, you can still use OSX Aegir, you'll just need to add a manual hosts entry for any hosts you want to access while disconnected.
Yes, I know. I still do all Drupal development on OSX Aegir. Indeed, for every site that I need to access offline, I add a line in the hosts file. Not ideal, but it works.
Response from applecare is that engineers said it's "Expected behaviour" no idea if they will ever fix it.. here is video I made showing the issue (no resolver available when you are disconnected from networks).
Well, that's the second time I experience such behavior from Apple. Half a year ago they screwed me by not providing a solution for my fried #MacbookPro2011 and now this. I'm starting to dislike the company more and more.
Any update on this?
@dave0783 supposedly you can workaround this using a loopback device, I've just not had enough time to try and figure it out.
Resolved as of 10.10.4 (14E26a), Apple have changed back to mDNSResponder instead of discoveryd!
Since I have a new retina Macbook (late 2013, instead of my old late 2011 model), dnsmasq isn't working anymore when I am not connected to the internet. I saw you already implemented what should be a solution, but apparently this doesn't work for me.
The weird thing is, that I installed Aegir on a fresh Mavericks installation (which also ran on my previous Macbook), so I would guess that the problem lies in the hardware configuration; the new macbook has no longer an ethernet connection, only wireless.
The wireless adapter uses 127.0.0.1 as DNS, so that is not the source of the problem.
Any ideas?