Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <3CF6B217.3060307@adacel.com>
Date: Fri, 31 May 2002 09:13:27 +1000
From: Michael Wardle <michael.wardle@adacel.com>
Organization: Adacel Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1
MIME-Version: 1.0
To: Michael Wardle <michael.wardle@adacel.com>
CC: cygwin@cygwin.com
Subject: Re: ssh and name resolution
References: <3CF57593.8020302@adacel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

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/