On Monday 07 April 2003 17:00, Ken Schneider wrote:
That is not correct. Since your computer nor your router know anything about the address it will search the internet to try and resolve the "hardware" address to the given "ip" address.
resolve hardware address? You mean arp? It won't. It knows enough about the ip address from looking at the routing table, which should tell it all it needs to know about how to handle it. I think the problem in this case is that those numbers after telnet aren't numbers, they're characters. It looks like telnet first tries to resolve those characters as though it were a text url. Only after that fails will it try to convert it into a quad IP address. An strace shows ftp does the same thing. ssh doesn't, for some reason. If you want it to happen faster you could set up a local forwarding dns, which should be able to answer quicker than the remote dns that it's a malformed url.