From 967ab6c797a2cfec3191f3f41076bcea1a21a6cb Mon Sep 17 00:00:00 2001 From: Dima Dorfman Date: Wed, 28 Mar 2001 03:56:24 +0000 Subject: [PATCH] Explain why it might be taking so long to connect to a telnet or SSH server (age-old DNS problem). Approved by: nik --- en_US.ISO8859-1/books/faq/book.sgml | 46 +++++++++++++++++++++++++++- en_US.ISO_8859-1/books/faq/book.sgml | 46 +++++++++++++++++++++++++++- 2 files changed, 90 insertions(+), 2 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index edf3a0a927..04f5aa127e 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -14,7 +14,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.160 2001/03/27 23:48:03 dd Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.161 2001/03/28 02:27:19 dd Exp $ 1995 @@ -4241,6 +4241,50 @@ IO range check 0x00 activate 0x01 + + + + Why does it take so long to connect to my computer via + &man.ssh.1; or &man.telnet.1;? + + + + The symptom: there is a long delay between the time the TCP + connection is established and the time when the client software + asks for a password (or, in &man.telnet.1;'s case, when a login + prompt appears). + + The problem: more likely than not, the delay is caused by + the server software trying to resolve the client's IP address + into a hostname. Many servers, including the Telnet and SSH + servers that come with FreeBSD, do this in order to, among + other things, store the hostname in a log file for future + reference by the administrator. + + The remedy: if the problem occurs whenever you connect from + your computer (the client) to any server, the problem is with + the client; likewise, if the problem only occurs when someone + connects to your computer (the server) the problem is with the + server. + + If the problem is with the client, the only remedy is to + fix the DNS so the server can resolve it. If this is on a + local network, consider it a server problem and keep reading; + conversely, if this is on the global Internet, you will most + likely need to contact your ISP and ask them to fix it for + you. + + If the problem is with the server, and this is on a local + network, you need to configure the server to be able to resolve + address-to-hostname queries for your local address range. See + the &man.hosts.5; and &man.named.8; manual pages for more + information. If this is on the global Internet, the problem + may be that your server's resolver is not functioning + correctly. To check, try to look up another host--say, + www.yahoo.com. If it doesn't work, that's + your problem. + + diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml index edf3a0a927..04f5aa127e 100644 --- a/en_US.ISO_8859-1/books/faq/book.sgml +++ b/en_US.ISO_8859-1/books/faq/book.sgml @@ -14,7 +14,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.160 2001/03/27 23:48:03 dd Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.161 2001/03/28 02:27:19 dd Exp $ 1995 @@ -4241,6 +4241,50 @@ IO range check 0x00 activate 0x01 + + + + Why does it take so long to connect to my computer via + &man.ssh.1; or &man.telnet.1;? + + + + The symptom: there is a long delay between the time the TCP + connection is established and the time when the client software + asks for a password (or, in &man.telnet.1;'s case, when a login + prompt appears). + + The problem: more likely than not, the delay is caused by + the server software trying to resolve the client's IP address + into a hostname. Many servers, including the Telnet and SSH + servers that come with FreeBSD, do this in order to, among + other things, store the hostname in a log file for future + reference by the administrator. + + The remedy: if the problem occurs whenever you connect from + your computer (the client) to any server, the problem is with + the client; likewise, if the problem only occurs when someone + connects to your computer (the server) the problem is with the + server. + + If the problem is with the client, the only remedy is to + fix the DNS so the server can resolve it. If this is on a + local network, consider it a server problem and keep reading; + conversely, if this is on the global Internet, you will most + likely need to contact your ISP and ask them to fix it for + you. + + If the problem is with the server, and this is on a local + network, you need to configure the server to be able to resolve + address-to-hostname queries for your local address range. See + the &man.hosts.5; and &man.named.8; manual pages for more + information. If this is on the global Internet, the problem + may be that your server's resolver is not functioning + correctly. To check, try to look up another host--say, + www.yahoo.com. If it doesn't work, that's + your problem. + +