From: Eric Hodel Date: 2005-11-11T09:42:46+09:00 Subject: Re: Network computer name problem w/ Tiger and DRb On Nov 10, 2005, at 3:29 PM, Jim Freeze wrote: > 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? Reverse DNS. You do a RDNS lookup when you look up by IP instead of by name: $ ifconfig fxp0 | grep inet inet 192.168.1.13 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::208:2ff:febb:cd4c%fxp0 prefixlen 64 scopeid 0x1 Reverse: $ host 192.168.1.13 13.1.168.192.in-addr.arpa domain name pointer RUR-3.coop.robotcoop.com. Forward: $ host rur-3.coop.robotcoop.com rur-3.coop.robotcoop.com has address 192.168.1.13 >>> 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? $ host `ifconfig | grep 'inet ' | grep -v '127' | cut -d ' ' -f 2` 70.1.168.192.in-addr.arpa domain name pointer kaa.coop.robotcoop.com. Should do it for BSDlike systems like your Mac. -- Eric Hodel - drbrain@segment7.net - http://segment7.net FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04