Why DNS in OS X 10.10 is broken, and what you can do to fix it
1–10 of 65 posts
Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it
#2Author is clearly holding it wrong, it just works, until it doesn't, then the user is still wrong.
Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it
#3I 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 may cause worse problems.
Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it
#4I've seen the Safari hangs -- sometimes it won't even open a new (empty!) tab. I knew it had to be network related, but forgot that discoveryd is in 10.10 or I would have suspected DNS right away.
edit: anyone remember how broken DNS would prevent you from being able to completely login to GNOME? That is what this feels like.
Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it
#5I 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.
Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it
#6This 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 has also made this clear here: http://support.apple.com/en-us/HT203136
Yosemite has split the job of unicast and multicast DNS up such that you cannot resolve single-label .local domains with unicast DNS anymore; you MUST use multicast. This is why hosts will resolve with nslookup or dig but not ping. The old behavior with mDNSresponder was arguably legacy backwards compatibility for unicast DNS resolution of .local hosts.
(I figured this out the hard way over a weekend using the Googles when my local VMs weren't resolving properly via dnsmasq - my fortunes changed when I looked into ".local").
There is one remaining problem with Yosemite DNS I haven't figured out yet, and that's getting unicast DNS resolution via dnsmasq while offline. Frustrating.
Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it
#7DNS is broken in 10.10? Haven't had a single problem...
Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it
#8I 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.
Yes, probably OS X is a bit left aside nowadays.
Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it
#9This 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?
Re: Why DNS in OS X 10.10 is broken, and what you can do to fix it
#10I'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.