Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why DNS in OS X 10.10 is broken, and what you can do to fix it

arstechnica.com

Post reply on HN
Print view View original

51–60 of 65 posts

Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it

#51

Post by FireBeyond »

parasubvert wrote: post #6

This article is at best misguided. OS X 10.10 DNS is not broken, it is working as intended - just differently from the past. Standards have changed and many haven't noticed. All of the bugs cited have to do with ".local" domains. You should never use .local domains as IANA has designated this domain as a special use domain for Multicast DNS as part of IP Zeroconf and Bonjour. http://tools.ietf.org/html/rfc6762 Apple…

"it is working as intended - just differently from the past"

This is blatantly wrong. Any device on my network (which uses .lan as a suffix) that sleeps (including Apple TVs) gets the dreaded "(2)" (or 3, 4, 7), before I started disabling "Wake for Network Access".

Yes, things are different. But don't pretend that we're just "doing/holding it wrong". There are things that are -very- broken.

Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it

#52

Post by FireBeyond »

webscale2015 wrote: post #5
rnhmjoj wrote: post #3

I had the " is already in use" problem, the safari not able to resolve any hostname and I could not use wake on demand for almost 2 years because of some bug. Maybe I am unusually unlucky but I agree that the quality of the last OS X releases has clearly got worse. The problem with apple software is that if it doesn't "just work" there is little to do about it. I am not so sure about reenabling mDNSResponder. This ma…

Their software has improved on the mobile front, it seems that's where all their engineers focus these days. It is sad that mac users long for the stability, speed and simple effectiveness of previous versions.

You don't use third party keyboards, then?

Because they regularly break. Swiftype, Swype. Keyboards disappear. All sorts of stuff.

And iOS 8 isn't really that much better. I've seen weird screens where all the apps are shown, in different orientations, text rotated while the app maintains a different orientation, in Apple apps and third party.

Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it

#53

Post by IgorPartola »

eridius wrote: post #39
IgorPartola wrote: post #31

Earlier quoted context omitted.

For you and others with similar issues, add this to your .bashrc: function restart-discoveryd() { sudo launchctl unload /System/Library/LaunchDaemons/com.apple.discoveryd.plist sudo launchctl load /System/Library/LaunchDaemons/com.apple.discoveryd.plist } Then simply run `restart-discoveryd` when you can't seem to ping google.com. I always struggle to remember how to start/stop things with launchd, so this is my litt…

Try just doing sudo discoveryutil udnsrestartquestions instead. The one time I had DNS issues (only once!), I ran that command and all of my DNS issues immediately resolved themselves.

I am not sure I understand what this command does, even after reading the man page for discoveryutil. Does it just restart any queries that have not been resolved, or does it restart the process as does my command? If it's the former, how does it work to fix whatever issues discoveryd is having?

Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it

#54

Post by eridius »

IgorPartola wrote: post #53
eridius wrote: post #39

Earlier quoted context omitted.

Try just doing sudo discoveryutil udnsrestartquestions instead. The one time I had DNS issues (only once!), I ran that command and all of my DNS issues immediately resolved themselves.

I am not sure I understand what this command does, even after reading the man page for discoveryutil. Does it just restart any queries that have not been resolved, or does it restart the process as does my command? If it's the former, how does it work to fix whatever issues discoveryd is having?

It almost certainly does not restart the process.

In my short time poking around, my belief is discoveryd gets wedged into a state where it thinks DNS queries aren't resolving, and so it doesn't try to resolve them. I'm not sure what exactly is going on there, either all the queries are blocked somehow on some long-lived query that has no response and no timeout, or discoveryd thinks the network is broken and is waiting for it to come back (those are just guesses). Either way, the command tells discoveryd to restart any outstanding "questions" (which presumably means queries). When I had the issue, that was sufficient to flush out whatever it was that was blocking everything, as my machine instantly started working properly again.

Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it

#55

Post by achivetta »

dfcowell wrote: post #36

What kills me about 10.10 is that OSX doesn't even try to resolve a domain name if you're offline. I run dnsmasq locally, which handles all of my DNS requests, capturing .dev domains (resolving them to 127.0.0.1) and forwarding everything else to Google's servers. This is great as long as I'm connected to WiFi or Ethernet (both are configurable through system preferences) but if I'm travelling and don't have an activ…

Do you have a bug number, by chance? (If not, consider filing one at bugreporter.apple.com)

Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it

#56

Post by MrBuddyCasino »

protomyth wrote: post #33
rayiner wrote: post #16

Earlier quoted context omitted.

Yosemite is very solid for me as long as it doesn't have to do with iOS integration. iOS 8 is shit-pure-shit, to the point where even my non-technical mother in law and wife have asked about downgrading. Seriously, random non-technical people I meet talk about how bad iOS 8 is and how they won't upgrade. I haven't seen anything like it since the Windows 9x era.

Yosemite's Finder is a continuous source of errors (move a lot of files and watch it crash, never mind the reversion in Applescript). It also has some problems with connecting to drives on a server.

I don't know anyone who doesn't have a paus alternative such as Forklift installed. Finder is probably the worst app Apple ever released.

Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it

#57

Post by realityloop »

dfcowell wrote: post #36

What kills me about 10.10 is that OSX doesn't even try to resolve a domain name if you're offline. I run dnsmasq locally, which handles all of my DNS requests, capturing .dev domains (resolving them to 127.0.0.1) and forwarding everything else to Google's servers. This is great as long as I'm connected to WiFi or Ethernet (both are configurable through system preferences) but if I'm travelling and don't have an activ…

I posted this issue on hn a week or so ago (https://news.ycombinator.com/item?id=8969581).. I tried via AppleCare to escalate this and the response from Apple engineers was that it's expected behaviour.. Also if not for a few key apps I'd be switching to some Linux variant.. Here is a video showing the bug with a comparison of 10.9 and 10.10 https://www.youtube.com/watch?v=3m9OI_AjCx8

Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it

#58

Post by protomyth »

MrBuddyCasino wrote: post #56
protomyth wrote: post #33

Earlier quoted context omitted.

Yosemite's Finder is a continuous source of errors (move a lot of files and watch it crash, never mind the reversion in Applescript). It also has some problems with connecting to drives on a server.

I don't know anyone who doesn't have a paus alternative such as Forklift installed. Finder is probably the worst app Apple ever released.

Well, buying a couple 100 copies of Finder replacements is not seen as a good use of money. Plus, training is an issue.

Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it

#59

Post by janfoeh »

silviogutierrez wrote: post #34
janfoeh wrote: post #28

Earlier quoted context omitted.

I got offline resolution with dnsmasq to work with # /usr/local/etc/dnsmasq.conf address=/.foobar/127.0.0.1 and # /etc/resolver/foobar nameserver 127.0.0.1

Odd, that's what I use: # cat /usr/local/etc/dnsmasq.conf address=/dev/127.0.0.1 # cat /etc/resolver/dev nameserver 127.0.0.1 Instead of your choice of foobar. Doesn't work offline. Your conf looks like the standard dnsmasq conf anyway, so maybe there's one other flag or configuration that you figured out?

I've searched high and low after reading your reply, trying for an hour to jog my memory of how I got that to work.

Well, I found it — quite a few entries in /etc/hosts, made at 02:30 AM, together with unflattering comments about the parents of those responsible for Yosemites new DNS subsystem...

So sorry for getting your hopes up! I have no idea how I could have misremembered all that so badly.

Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it

#60

Post by [deleted] »

gurkendoktor wrote: post #11
parasubvert wrote: post #6

This article is at best misguided. OS X 10.10 DNS is not broken, it is working as intended - just differently from the past. Standards have changed and many haven't noticed. All of the bugs cited have to do with ".local" domains. You should never use .local domains as IANA has designated this domain as a special use domain for Multicast DNS as part of IP Zeroconf and Bonjour. http://tools.ietf.org/html/rfc6762 Apple…

That sounds like a good reason/background story for Apple to change the existing mDNSresponder, but how are the issues in the article not signs of 10.10 being broken? (The article was written before 10.10.2 was released, so some bugs might have been fixed.) I think the only misguided part was to encourage people to replace system files.

[deleted]
Post reply on HN