From: Eric Hodel <drbrain@...7.net>
Date: 2005-11-11T08:14:53+09:00
Subject: Re: Network computer name problem w/ Tiger and DRb

On Nov 10, 2005, at 2:59 PM, Jim Freeze wrote:

> On 11/10/05, Eric Hodel <drbrain@segment7.net> wrote:
>> On Nov 10, 2005, at 2:38 PM, Jim Freeze wrote:
>>
>>> While running DRb, I noticed that a timeout was occuring with the  
>>> URI
>>> provided by DRb.uri. On my powerbook, DRb returned as the URI:
>>>
>>>    druby://<computer_name>.local:port
>>>
>>> Executing the first remote call within DRb took over a minute on
>>> my powerbook, but was instantaneous on my sun box.
>>
>> Sounds like your DNS is not completely configured.
>
> The PowerBook DNS? BTW,  I am attaching to my company network.
>
>>  From the sun, what does `host ip.ad.re.ss` (or dig or nslookup)
>> where ip.ad.re.ss is the address of the powerbook return?
>
> It says:
>
> % host /jim-freezes-powerbook-g4-15.local
> Host /jim-freezes-powerbook-g4-15.local not found: 3(NXDOMAIN)

A failure with your IP address is more informative.  I wouldn't  
expect every DHCP server to properly update DNS when it hands out  
leases.

> But DRb still works, it just has to wait for a timeout  for the first
> remote call.
> All subsequent calls are fast.

Right, DRb does an RDNS lookup to figure out the local host name,  
which probably takes forever.

>> If you don't have matching forward and reverse DNS, DRb won't be able
>> to return a good hostname.
>
> Since the computer connects with DHCP to the network, adding host  
> entry
> won't help here. And, I don't think I should have to run bind on my
> laptop to get this to work.
>
> Any suggestions?

The DHCP address you're handed should have matching forward and  
reverse DNS.  Complain to your network admins.

-- 
Eric Hodel - drbrain@segment7.net - http://segment7.net
FEC2 57F1 D465 EB15 5D6E  7C11 332A 551C 796C 9F04