In Yosemite 10.10.5 .local addresses worked fine (not in the first Yosemite releases though). In El Capitan it stopped working again.
@Apple: Could you please fix this in the next update? :-)
I know .local addresses are not the standard way and something you should avoid but tell that to our IT department ;-)
MacBook Pro with Retina display, OS X El Capitan (10.11)
Hi AndreasBSweden,
I see that you are having some issues with .local addresses in El Capitan. Here is an article with some guidance on addressing this issue:
If you're unable to resolve or bind to domains that end in .local - Apple Support
https://support.apple.com/en-us/HT203136
Thanks for being a part of the Apple Support Communities!
I've seen this solution before but as it is now i'm a bit in the hands of our IT department that won't make any changes soon due to so many systems that will be affected. They have however made some small changes that has helped some. I know that in Yosemite 10.10.4 or 10.10.5 Apple changed back to another process (the old one for network discovery/resolves) where .local addresses actually still worked. Couldn't one make some other workaround for now or maybe in the next El Capitan update? 🙂 Another thing is that kinit command (kerberos) also is broken so I have issues with authentication now against our AD network, but I suspect that is also related to the same change...
El Capitan - .local addresses stopped working, again
