This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: ssh and name resolution
- From: Michael Wardle <michael dot wardle at adacel dot com>
- To: Michael Wardle <michael dot wardle at adacel dot com>
- Cc: cygwin at cygwin dot com
- Date: Fri, 31 May 2002 09:13:27 +1000
- Subject: Re: ssh and name resolution
- Organization: Adacel Technologies
- References: <3CF57593.8020302@adacel.com>
Michael Wardle wrote:
> I have a local host called "meerkat" that I want to connect to via ssh.
> When I issue "ssh meerkat", I get a warning:
> "The authenticity of host 'meerkat(202.50.84.15)' can't be established"
> Yet meerkat is a host on my local 192.168.x.x subnet.
> "nslookup meerkat" returns the expected IP address in 192.168.x.x.
Thanks to all who replied so far, but you've all missed the point:
when I "ssh meerkat", I am connecting to a different host than the
meerkat I expected.
ping meerkat gives one host (202.50.84.15)
nslookup meerkat gives another (192.168.x.x)
Is there anything special I need to do to make name resolution work as
expected?
--
MICHAEL WARDLE
SGI Desktop & Admin Software
Adacel Technologies Limited
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/