Mac – Workaround for using “.local” as a Leopard Server’s hostname

macmac-osxosx-leopard

Using ".local" as your hostname breaks Kerberos (and other services) in Mac OS Server 10.5 Advanced because the server will only do Bonjour lookups instead of checking with the DNS Server(s). There is an old Apple knowledgebase article (from OS 10.3) that says adding the string "local" to the "Search Domains" section of the Network System Preference Pane will force your computer to lookup via a DNS server instead of just Bonjour…

…which sounds like it would also allow you to use "server.local" as your hostname – can anyone confirm this is the case, or is there some other drawback with this workaround?

Best Answer

If your internal domain is .local, you will have a problem resolving names via DNS. There is an old article on Mac OS X Hints which describes a solution:

I created a company.local file in /etc/resolver, and populated this file with the nameservers for the company.local AD domain. This allows Mac OS X to use standard DNS to resolve company.local (or subdomain.company.local), while still allowing Rendezvous to operate as expected.

The only drawback I've seen to this approach is that the nameservers in this company.local file don't update via DHCP, so I have to update them manually.

Here is a more official support document from Apple which will parse your existing /etc/resolv.conf to populate the file in /etc/resolvers.

Related Topic