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

11–20 of 65 posts

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

#11

Post by gurkendoktor »

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.

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

#12

Post by protomyth »

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.

I wouldn't say that. We are still experiencing the iOS won't connect to wifi bug. The really chaotic thing is that iPhones or iPads of the exact same model and software revision (current iOS 8.1.3) will randomly connect, not connect, or connect long enough to get an ip address then not be able to do anything. It is really getting quite frustrating. We have a Cisco 5807 controller and the 3702e wireless points. Every other OS works just fine. Only having trouble with Apple products and randomly at that.

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

#13

Post by headwayoldest »

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.

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

#14

Post by nezza-_- »

oe wrote: post #9
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…

My Yosemite fails frequently resolving common domain names (.com). Has that something to do with .local domains and how could I fix it?

This most likely has to do with your DNS server. Try to change it to another one (e.g. Google's 8.8.8.8 or OpenDNS's 208.67.222.222) and see if it gets better.

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

#15

Post by twoodfin »

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…

In my experience, discoveryd is at best at about the quality of beta software. With some regularity on several different Macs on different networks, it completely loses the ability to resolve names. Kill it and let launchd restart it, and suddenly names resolve again.

Another Yosemite daemon addition, recentsd, had serious issues (for example: substantial memory leaks when interacting with Mail.app) until 10.10.2.

Apple has gotten very good at eliminating crashes. They're obviously using the reporting mechanism there to great effect. But at the same time, Console.app has never been noisier, and failures that don't result in crashes seem to linger far too long.

They've also become, it seems, far more dependent on an "orchestra" of daemon processes to perform tasks that in the past would have been implemented in passive frameworks used separately by each app. That adds complexity of coordination, and meanwhile a single failure can affect every "client" app on the system.

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

#16

Post by rayiner »

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.

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

#17

Post by smackfu »

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…

>DNS is not broken, it is working as intended - just differently from the past.

Yeah, but the rewrite is buggy as rewrites often are. If it worked as intended, I doubt so many people would have so many problems.

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

#18

Post by smackfu »

NietTim wrote: post #7

DNS is broken in 10.10? Haven't had a single problem...

That's the problem with networking, right? That the environments you are running in are so diverse that it's nearly impossible to test all the situations. I'm sure that the Apple testers didn't think it was buggy before they released it but a lot of people are having issues in real world situations where the old system worked fine.

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

#19

Post by winthrowe »

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.

No, Microsoft has not been recommending .local, as this document, circa Windows Server 2000, states:

> Identify your organization's DNS owner and determine what registered DNS names you have available on the network that will host Active Directory.

> If you do not have a registered domain name, you should register a name with an Internet DNS registration authority.

https://technet.microsoft.com/en-us/library/bb727085.aspx

>

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

#20

Post by engi_nerd »

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.

Post reply on HN