Problems with Mac OS X Clients

[Sten Carlsen]

Hi
When I got my MAC, I used .local as my local in-house top level domain.
My hosts were called host1.home.local. This was done to be sure that any
reference to my local network would not resolve or be routed anywhere on
the outside.

Then I got my MAC and nothing worked for it, all else worked as usual.
After some searching and reading I figured out that Apple uses .local to
signify locally defined names so you can find all printers or whatever,
just by doing a mDNS lookup.

Once I realised this I changed all internal names to xxx.home and
everything worked also the MAC.

Later I changed everything to my now real domain name (.dk) and no
problems have turned up since then.

So; if you don't use .local internally for any purpose (except
rendevous) don't worry about this.


Adrian Merwood wrote:
> Sten Carlsen wrote:
>   
>> Hi
>>
>> You don't have .local as your local "safe" tld?
>>
>> Mac-OSX does have a special meaning with this tld. Rendevous. I did this
>> when I first bought a MAC, it took me a day to figure out what the
>> problem was. I had similar problems.
>>
>> The solution is DON'T use .local as tld.
>>
>> If that is not what you do, you have other problems I have no clue about.
>>
>>
>>
>> Adrian Merwood wrote:
>>   
>>     
>>> Hi,
>>>
>>> I am running 2 different (alternating) DHCP 3.0.3 servers - 1 on 
>>> Mandrake 2006 and 1 on CentOS.  They both exhibit the same behaviour.  
>>> They will happily serve up DHCP addresses to anything on my network 
>>> except for the OS X systems.  I see the following sequence in the log 
>>> when I try to request DHCP address from my OS X laptop:
>>>
>>> May  6 20:15:32 gateway dhcpd: DHCPREQUEST for 192.168.1.64 from 
>>> 00:16:cb:07:49:93 via eth1: lease 192.168.1.64 unavailable.
>>> May  6 20:15:32 gateway dhcpd: DHCPNAK on 192.168.1.64 to 
>>> 00:16:cb:07:49:93 via eth1
>>> May  6 20:15:32 gateway dhcpd: DHCPDISCOVER from 00:16:cb:07:49:93 via eth1
>>> May  6 20:15:32 gateway dhcpd: DHCPOFFER on 192.168.1.195 to 
>>> 00:16:cb:07:49:93 via eth1
>>> May  6 20:15:33 gateway dhcpd: DHCPDISCOVER from 00:16:cb:07:49:93 via eth1
>>> May  6 20:15:33 gateway dhcpd: DHCPOFFER on 192.168.1.195 to 
>>> 00:16:cb:07:49:93 via eth1
>>> ....and so on
>>>
>>> The 192.168.1.64 address is from another network served by a built in 
>>> DHCP server on an ADSL router which happily serves up addresses to OS X.
>>>
>>> I am at a loss to explain why simplistic built in DHCP servers such as 
>>> the one in my Router work but the bog standard ISC DHCP server on either 
>>> of my linux systems will not work with the OS X dhcp client?
>>>
>>> Any and all suggestions would be most welcome.
>>>
>>> Adrian
>>>
>>>   
>>>     
>>>       
>>   
>>     
> Sten,
>
> I am not sure what you mean by "safe tld" I have a real domain that I 
> use for most machines, mind you I am not sure how I set the domain on 
> the mac to what I want? 
>
> Please can you elaborate......it has crossed my mind that Rendezvous 
> might be casuing this.
>
> Adrian
>
>