You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
In my company we use a lot of .local domain for internal services.
With maverick i have access to this domains, but with yosemite i didn't have access.
I already try to look at mDNSResponder by did'nt find why this didn't work with all the "*.local" domain 😟
MacBook Pro (Retina, 13-inch, Late 2013), OS X Yosemite (10.10)
We found a solution that worked for us!
After running
sudo discoveryutil mdnsactivedirectory yes
in the terminal we're able to resolve .local FQDNs again. This gets it to use regular (unicast) DNS for .local domains rather than just using multicast DNS (mDNS, aka Bonjour) to look-up .local addresses.
Worked!
Adding the host names to search domains resolved this.
Apple needs to revert changes made that caused this...
MacBook Pro - Yosemite 10.10
For those who had success with the discoveryutil approach:
Place the following file in /Library/LaunchDaemons: https://gist.github.com/CodingMinds/509bd12a7c7e22f0cfdd
Thanks for the tip. It work on the first go.
THANK YOU! THANK YOU! THANK YOU! I thought I was going crazy. This solved the problem instantly. 😍😎
FWIW, I have discovered that this problem also affects iOS 8.1.
For those of you who can reproduce this problem, has the 10.10.1 update resolved the issue?
Thanks!
No, it did not. In fact, it seems like it reverted the manual change to the setting that did resolve it.
And it would be very friendly from Apple to give some reply on these posts since this fact really ***** for every business user...
I can not and will not upgrade due to this reason....
Do you have Sophos AV installed?
Add
127.0.0.1
.local
and ip-range e.g. 192.168.1.0/24
to the allowed websites or turn off web protection
Good luck
works for me thanks
Thank you, that worked well as a temporary workaround.
Trouble to access ".local" domain
