Shyamal Prasad <[EMAIL PROTECTED]> wrote: > "Rupert" == RUPERT LEVENE <[EMAIL PROTECTED]> writes:
> Rupert> Shyamal Prasad <[EMAIL PROTECTED]> wrote: > >> "Rupert" == RUPERT LEVENE <[EMAIL PROTECTED]> writes: > Rupert> Antony Gelberg <[EMAIL PROTECTED]> wrote: > >> >> On Sat, Aug 16, 2003 at 12:25:16AM +0100, > >> >> [EMAIL PROTECTED] wrote: > >> Running strace telnet localhost 22 shows that it's trying > >> to resolve the hostname localhost by querying the > >> nameserver. I thought that shouldn't happen with my setup, > >> though. > The mystery deepens since I looked at your configs and compared with > mine, and they are the same. The thing is, uh, when I run strace I see > the same thing happen. I can see a query going to my local name > server. > I've never noticed this because (a) I don't use telnet and (b) my > nameserver responds quickly enough that I don't notice any wierd > delay. > Now I'm really interested in the solution for your problem. Sorry I > can't give you a solution ;-) > Incidentally, ssh does not do this odd lookup and works exactly how > I'd have expected telnet to. Indeed. Netcat and galeon appear to do the right thing too, while telnet, lynx and links all suffer from a delay. (I first noticed the problem using lynx). My guess at the moment is that the combination of a slow machine and a slow nameserver is exposing an odd bug in these programs. Although I would be surprised if this were the case since telnet and lynx have such a long pedigree... Rupert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
