Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 4 Nov 2002 13:10:23 +0100
From:      Roman Neuhauser <neuhauser@bellavista.cz>
To:        Michael Joyner <mjoyner2@hq.dyns.cx>
Cc:        joe <joe-dated-1036563834.f2333b@dubium.com>, freebsd-questions@freebsd.org
Subject:   Re: SSH Delay problems
Message-ID:  <20021104121023.GC68683@freepuppy.bellavista.cz>
In-Reply-To: <1036131758.3dc21dae54439@imp.hq.dyns.cx>
References:  <200210312158.47996.joe@dubium.com> <200211011712.03207.jrhoden@unimelb.edu.au> <200210312222.08082.joe@dubium.com> <1036131758.3dc21dae54439@imp.hq.dyns.cx>

next in thread | previous in thread | raw e-mail | index | archive | help
# mjoyner2@hq.dyns.cx / 2002-11-01 01:22:38 -0500:
> Quoting joe <joe-dated-1036563834.f2333b@dubium.com>:
> > On October 31, 2002 10:12 pm, Jacob Rhoden wrote:
> > > On Fri, 1 Nov 2002 16:58, joe wrote:
> > > > There is a significant delay before ssh connects and returns a
> > > > prompt. I am on a private network, attempting a 192.168.0.XXX
> > > > 192.168.0.YYY connection.   There is a distinct 1:15 min delay
> > > > before the password prompt appears.  I have included the log of a
> > > > specific session.
> > >
> > > Summary of last thread: If your dns isnt setup properly then there
> > > will be a delay in connecting to the server. The reason for this is,
> > > the remote server is attempting to resolve the local machines ip
> > > address. If setup properly, it will resolve straight away. If dns is
> > > not setup properly, it tries and gives up (after about approximately
> > > 1:15 minutes I would suspect).
> > >
> > > You need to check the remote machine can resolve your local ip
> > > address. To test this on your remove machine type:
> > >
> > >    nslookup 192.168.local.machine.ip.address
> > 
> > Sorry, I should have mentioned these two machines are behind a firewall 
> > and use private ip addresses. The hosts files identify each other 
> > properly. Even if I attempt a connection using the ip address  I 
> > observe the same problem. Do you still think this is a DNS issue?  I'm 
> > not sure how it would be.
> 
> Sounds like a DNS issue to me! :)
> 
> You need to setup a local bind that will resolve and reverse resolve
> all your private #'s

    note that it doesn't need to be Bind, you can use any DNS server.
    djbdns has been doing me a very good service:

    http://cr.yp.to/djbdns.html

-- 
If you cc me or take the list(s) out completely I'll most likely ignore
your message.      see http://www.eyrie.org./~eagle/faqs/questions.html

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021104121023.GC68683>