It's both. The host is Sweden tries to do a reverse lookup on you when you
telnet or ftp to it, and your DNS isn't set up to respond to a reverse
lookup. Without knowing quite a bit about how you do DNS, I can't guess the
details or the fix.
In the other direction ... I'd guess that your host is also trying to do a
reverse lookup, but that the host is Sweden has its DNS set up properly to
answer a reverse-lookup request. Or it's possible, if les likely, that your
system isn't doing a reverse-lookup check on incoming connections.
Typically, both telnet and ftp are run as inetd services, and both typically
use tcpd to screen connection attempts. It's tcpd that's making the actual
reverse lookup request. In contrast, httpd is typically run standalone, and
turning off reverse lookup (it's an option in Apache) is a standard way to
speed up Web server responsiveness.
At 01:06 PM 2/28/00 +0800, Niclas Hedhman wrote:
>
>If I from my Linux box, envision.asiaconnect.com.my, in Malaysia do
>
>telnet l2w204.medab.se
>
>to a Linux box in Sweden, the connection takes about one minute or so.
>FTP is the same, HTTP a lot faster.
>
>But if I from that machine telnet or ftp back to the Malaysian host, the
>connection is up in a second or two.
>
>I can only explain this by it has something to do with reversed DNS
>resolution, and my questions are...
>
>a) Does it? If not, what else could it be...
>b) And in which network, Malaysia or Sweden?
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
