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

41–50 of 65 posts

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

#41

Post by lectrick »

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…

Are you sure that intermittent failure to name-resolve can solely be attributed to the handling of .local domains? It seems that if that was the case, the failures would be more deterministic

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

#42

Post by sproutworks »

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've been using my Zyxel travel router to access the internet with my iMac until the wifi issues are resolved.

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

#43

Post by MarcScott »

The networking issues with Yosemite were the final push I needed to shrink it down to a tiny partition and install Linux on my MBP.

I'm a very happy MBP user now, and having a tiling windows manager is such a productivity boost, I doubt I'll ever go back.

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

#44

Post by munchhausen »

To be fair, innovation and replacing battle-hardened^W^Wobsolete system components with new software that's pushing the envelope comes at a cost. Apple are doing the right thing here and at this pace, I can see OSX being ready for the desktop soon. I'm not replacing my Ubuntu box with a Mac just yet, as some of my core productivity apps have a dependency on DNS, but I'll be keeping a close eye on OSX for sure.

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

#45

Post by wvenable »

headwayoldest wrote: post #13
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…

The counter argument to this is that the RFC is exceedingly new, and directly from Apple. Microsoft has been using .local in example (and recommending them for production) AD builds for a decade. I see what Apple is going for, and I don't mind the idea, but the practical results are frustrating and pointless.

.local doesn't work in Windows either as of Windows 8.

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

#46

Post by hackuser »

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…

> 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

That may be the official standard, but .local is a very common, de facto standard. Products need to be compatible with reality.

Just glancing at the RFC, is my impression correct that in February 2013, with .local already widely used for private domains, someone published an RFC appropriating the name for something else? (Could they have used a different name?) They expect the world to change their internal domains in order to accommodate their new idea?

Is there a standard for private second-level domain names? I've never seen one.

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

#47

Post by xtreme »

engi_nerd wrote: post #20

I eagerly await a true fix to 10.10's issues with dropping wifi connections. Both Macbooks in my house running 10.10 drop the wifi connection at least 5x/day, often more. My other devices do not experience these drops, and these same machines were just fine on 10.9. My opinion of Apple's software quality has decreased over the past few months.

I believe it has something to do with automatic selection of the 2.4 GHz or the 5 GHz band. Unfortunately, Apple does not provide any API to control which band is selected.

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

#48

Post by parasubvert »

lectrick wrote: post #41
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…

Are you sure that intermittent failure to name-resolve can solely be attributed to the handling of .local domains? It seems that if that was the case, the failures would be more deterministic

Multicast DNS isn't very predictable.

I have no bad experiences with resolving regular domains on Yosemite, but others in this tread have suggested bouncing discoveryd can help.

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

#49

Post by parasubvert »

rayiner wrote: post #16
untog wrote: post #10

I've come to the realisation that I don't trust Apple software much these days. I used to upgrade to the latest version of both phone and computer OS quickly, but these days I'll hold on as long as I can - I'm still on 10.9, and waiting for the inevitable software upgrade that will make me have to pull the trigger. I miss the Snow Leopard days.

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.

iOS 8 has had problems in early point releases but it's apprently now on 67% of iOS devices. I've found it a bit more stable and usable than iOS 7 but I am on a 5S and 6.

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

#50

Post by ecnahc515 »

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 ran into the same problem with Yosemite when offline in a plane this weekend. I'm using the same setup as you except I have .dev instead of just dev.
Post reply on HN