Trouble to access ".local" domain

Hi Ulzuraj many thanks for the information! You are right, I tried to insert the records

like this: 192.168.3.123 frodo.shire frodo
and there is no need to insert two identical records, one for the machine name and one full.
Now with frodo.shire the resolution is both frodo and frodo.shire.
Thank you for your contribution.

Use "local" as the domain name of the local network is not a good idea 😕

I have this problem as well, and the "sudo discoveryutil mdnsactivedirectory yes" command does not fix it.

I have an added layer in that I'm using a VPN (Cisco AnyConnect), so the VPN software probably makes its own changes to how the resolver is working.

I can temporarily fix this using:

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist

sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist

Within a few minutes, I'm back to broken name resolution. Maybe if I just leave discoveryd off? I suppose then I have to live without AirPlay and other goodies.

I upgraded to Yosemite from Mountain Lion, due to Mavericks having a display driver problem which caused GoToMeeting to crash. Yosemite fixes that, but now I can barely access my intranet! Ugh.

I know, the real fix is to get my IT department to use something other than "companyname.local" for its intranet.. but that ship turns slowly.

Hi,

I updated my MacBook Pro from 2007, to Yosemite 10.1 and did some tests.

- the WiFi is not dropped anymore after the computer goes to sleep - SOLVED

- the computer name is not changed anymore and the computer name <name> is the same as <name>.local. Non numbers or anything. The name stays the same during the day, after reboots and for different users. Rock solid. - SOLVED

The conclusion is that the 10.1 update solved the problems above and I would recommend an update.

Jonas

Sweden

I Updated to Yosemite 10.10.1 to test this and the update has removed the .local address workaround I had added in the search domains.

Still seems that adding the address to the search domains is the only workaround, otherwise changing the address to something other than .local.

Apple need to fix this! Hopefully the next patch will resolve this.

AD has been using .local domains since 2000. Is it necessarily "best practice?" Probably not, but until very recently it wasn't a problem, or in direct opposition to any RFC. Just because an Apple employee decides to write an RFC that is less than 2 years old without taking into consideration 10+ years of enterprise networking does not make it APPLE = RIGHT and the AD infrastructure = WRONG.

There are plenty of domains in the enterprise world using .local tlds. MDNS is not an enterprise feature, it is for small networks and home users who don't understand how to setup DNS properly. If Apple wants to use it - great, but their insistence that it should be forced onto an enterprise network that works 100% appropriately with a .local TLD is misguided. It is another example of Apple's horrific support and understanding of enterprise needs.

If you were building a new domain, I wouldn't recommend .local - mostly due to issues like this and the more technically sound argument being put out by CABrowser regarding the insecurity of SSL certs for .local environments (this I can buy into). But the reality is I have a .local running in my home lab because I have plenty of software customer with .local (and no, I didn't set up their environments). Windows servers get upgraded from 2000 > 2003 > 2008 > 2012 but the original domain names often stay and it can be a herculean effort to rename them in many cases.

Apple's insistence on what they believe is the "right way" is simply wrong. Enterprise friendly vendors need to live in the past as much as they have a foot in the future.

I have been trying to set up a number of macs so that can access pc on a windows network when then have a sslvpn setup. I have had no issue on older versions on the osx but Yosemite I have been unsuccessful. I can map drives or remote desktop with ip no problem, but not by name.

I can run sudo discoveryutil mdnsactivedirectory yes and I am able to use pc name, but after reboot I have to run this again, so not the best option.

I have tired creating the com.fix.local.plist and saving it in /Library/LaunchDaemons but on reboot it doe not work.

Is there a step I missed?

as to the .local issue, yes if I was to setup the netowrk today I would not use the .local but since this was setup in 2000 and the network has grown since then to change to not use the .local would be way to much work to just fix an issue with apple os.

Hi,

Have you tried using the full public domain name instead? I had to in my LAN server.local did not work but the public domain name did.

Jonas

Sweden

I have tried using just the .local name, <server>.local but no luck. It still doesn't bring any of them up. Any solutions yet?

Apple, please fix this!

Works for me!

Where did you find the solution?

Works for me also ! Thank you !

Do we have to run this command each time the network configuration changes ?

Solve to me!