Slow response to SSH from within network?

[Ansar Mohammed]

The DNS is really to avoid using hosts files. As long as the sshd process can
properly resolve your name-ip, you should be in business.

I used both host entries and DNS. I found that the best response was with the
DNS properly configured.

The other thing to note is that most DSL routers have *really* bad DNS
services.

I always turn off DNS proxy in any DSL/cable modem and use either the ISP or
an internal DNS.


-----Original Message-----
From: owner-tlug-lxSQFCZeNF4 at public.gmane.org [mailto:owner-tlug-lxSQFCZeNF4 at public.gmane.org] On Behalf Of James Knott
Sent: July 27, 2005 12:06 PM
To: tlug-lxSQFCZeNF4 at public.gmane.org
Subject: Re: [TLUG]: Slow response to SSH from within network?

Ansar Mohammed wrote:
> I think the solution is to install dns on your ssh server. Create your own
> internal dns zone and make entries for all your internal hosts.
>
> I had this problem a while ago when I upgraded to FreeBSD 5.4. That or
> removing the "dns" entry in nsswitch.conf was the only solutions.

I regularly use ssh, withot a DNS and no delay.  I'm running SuSE.
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3038 bytes
Desc: not available
URL: <http://gtalug.org/pipermail/legacy/attachments/20050728/7011f25b/attachment.bin>