«

Hi

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>.localort

Executing the first remote call within DRb took over a minute on
my powerbook, but was instantaneous on my sun box.

When I changed <computer_name> to <ip.ad.re.ss>, the delay
issue disappeared.

Thinking it may be a configuration issue, I fiddled with

Socket.do_not_reverse_lookup =3D true

but did not had any luck.

This is disconcerting since I had hoped that DRb.uri would return a
good address.

Does anyone know what the problem is here?

Thanks

--
Jim Freeze

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>.localort
>
> 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.

> When I changed <computer_name> to <ip.ad.re.ss>, the delay
> issue disappeared.
>
> This is disconcerting since I had hoped that DRb.uri would return a
> good address.
>
> Does anyone know what the problem is here?

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?

If you don't have matching forward and reverse DNS, DRb won't be able
to return a good hostname.

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

On Thursday 10 November 2005 3:38 pm, Jim Freeze wrote:

> When I changed <computer_name> to <ip.ad.re.ss>, the delay
> issue disappeared.
>
> Thinking it may be a configuration issue, I fiddled with
>
> Socket.do_not_reverse_lookup = true

This sounds like a simple DNS lookup issue with computer_name.

That'd be the first place I would investigate, anyway.


Kirk Haines

On 11/10/05, Eric Hodel <> 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>.localort
> >
> > 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)

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

> 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?
--
Jim Freeze

BTW, host failed, but dig seems to work:

% dig 'jim-freezes-powerbook-g4-15.local'

; <<>> DiG 9.2.2 <<>> jim-freezes-powerbook-g4-15.local
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50543
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;jim-freezes-powerbook-g4-15.local. IN A

;; AUTHORITY SECTION:
539 IN SOA frootb.mycompany.net.
dnssupport.mycompany.com. 2004059055 14400 3600 604800 600

;; Query time: 66 msec
;; SERVER: 10.208.0.3#53(10.208.0.3)
;; WHEN: Thu Nov 10 17:00:07 2005
;; MSG SIZE rcvd: 130

--
Jim Freeze

On Fri, 2005-11-11 at 08:01 +0900, Jim Freeze wrote:
> BTW, host failed, but dig seems to work:

No, this dig output shows that there is no answers to your query. So the
look up failed.

>
> % dig 'jim-freezes-powerbook-g4-15.local'
>
> ; <<>> DiG 9.2.2 <<>> jim-freezes-powerbook-g4-15.local
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50543
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
^^^^^^^^^^^^^^^^^^^

>
> ;; QUESTION SECTION:
> ;jim-freezes-powerbook-g4-15.local. IN A

This is your question/query.

No ANSWER SECTION.

HTH,
Guillaume.

>
> ;; AUTHORITY SECTION:
> . 539 IN SOA frootb.mycompany.net.
> dnssupport.mycompany.com. 2004059055 14400 3600 604800 600
>
> ;; Query time: 66 msec
> ;; SERVER: 10.208.0.3#53(10.208.0.3)
> ;; WHEN: Thu Nov 10 17:00:07 2005
> ;; MSG SIZE rcvd: 130



> --
> Jim Freeze
>

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

> On 11/10/05, Eric Hodel <> 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>.localort
>>>
>>> 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 - - http://segment7.net
FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04

On Nov 10, 2005, at 3:01 PM, Jim Freeze wrote:

> BTW, host failed, but dig seems to work:
>
> % dig 'jim-freezes-powerbook-g4-15.local'
>
> ; <<>> DiG 9.2.2 <<>> jim-freezes-powerbook-g4-15.local
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50543
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
^^^^^^^^^

ANSWER would be 1 if it found a matching record.

> ;; QUESTION SECTION:
> ;jim-freezes-powerbook-g4-15.local. IN A
>
> ;; AUTHORITY SECTION:
> . 539 IN SOA frootb.mycompany.net.
> dnssupport.mycompany.com. 2004059055 14400 3600 604800 600
>
> ;; Query time: 66 msec
> ;; SERVER: 10.208.0.3#53(10.208.0.3)
> ;; WHEN: Thu Nov 10 17:00:07 2005
> ;; MSG SIZE rcvd: 130
>
> --
> Jim Freeze

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

On Fri, 2005-11-11 at 07:59 +0900, Jim Freeze wrote:

> > 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.

Not on your laptop. But your DHCP server and you DNS server should
probably talk to each other so that:

1) your laptop gets a meaningful domain name (I doubt 'local' is it)
2) have the DNS server know about the IP given away by the DHCP server.

If you are using dhcpd by isc.org, lookup the 'DYNAMIC DNS UPDATES'
paragraph in the dhcpd.conf(5) man page.

Guillaume.

> Any suggestions?
> --
> Jim Freeze
>

On 11/10/05, Eric Hodel <> wrote:

> > 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.

What is RDNS. Is there a command line version of this so I can
see it work?

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

Yes. I will. Is there a commandline app that will show that a matching
reverse DNS is not being provided? Or just a dig failure?


--
Jim Freeze