From owner-freebsd-stable Tue Feb 27 14:39:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 05C5137B719 for ; Tue, 27 Feb 2001 14:39:18 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f1RMd2V66683; Tue, 27 Feb 2001 14:39:02 -0800 (PST) (envelope-from dillon) Date: Tue, 27 Feb 2001 14:39:02 -0800 (PST) From: Matt Dillon Message-Id: <200102272239.f1RMd2V66683@earth.backplane.com> To: David Malone Cc: Nate Williams , Rich Morin , freebsd-stable@FreeBSD.ORG Subject: Re: Curious delay in telnet References: <15003.57375.775222.91091@nomad.yogotech.com> <20010227222931.A55112@lanczos.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I don't think that will help 'cos the delay looks like it is with :the telnetd at the far end trying to look up the name, not the :local telnet. Unfortunately telnetd doesn't seem to have an option :corrisponding to -N. : : David. It's the telnet on the end trying to do a reverse-IP lookup of your IP address. Generally a delay like this means that you do not have your DNS setup properly to allow the remote end to do a lookup of your IP. The reverse setup is something that you have to work out with whomever owns your IP address space (typically your ISP or colo-facility). If you own the IP space directly, then there's probably a broken delegation somewhere. Alternatively, your reverse IP may work fine from external hosts but the DNS resolver on the particular destination you are telneting to is broken. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message