Live data from Hacker News

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

arstechnica.com

21–30 of 65 posts

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

#21

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.

The approved standard RFC is new but the proposal RFC and the practice of using .local for mDNS, like the convention of using .local for AD, goes back more than a decade. I agree that the whole thing is silly and pointless but it's not clear who "barged in" on whom.

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

#22
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.

Well, Snow Leopard had is problems as well: "Data losses in Snow Leopard bug" http://news.bbc.co.uk/2/hi/8304229.stm

I'm going in the other direction. Used to always wait one or two versions before upgrading and always doing a clean install. I installed bot Mavericks and Yosemite over the older versions early on without any problems.

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

#24
post #17

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.

I haven't had or heard of anyone having DNS problems personally in 10.10 and I have quite a few clients using it.

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

#25

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.

Which Macbooks do you have? This hasn't happened to me, but I'd like to know if it might.

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

#26

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.

My 10.10 used to crash after every VNC session ended. There was no info on Google about this, but there were hundreds of other bugs, seems like everyone has adopted one.

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

#28

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…

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

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

#29

Earlier quoted context omitted.

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…

Agree, having wifi problems myself, pretty much have to restart it on every use and that seems to get me around it until the next time it sleeps. I'm at the point of considering going back to iOS 7 on all my devices.

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

#30
post #9

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?

Had the same problem popping up just after upgrading to Yosemite. Decided to do a clean install a couple of months ago as I saw other machines on my network didn't have this problem. After the clean install things are working out as expected again.

Not what I really wanted (checked quite a bit around for a solution without finding any), but at least I don't have this happening multiple times a day.

Post reply on HN