DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:content-type
	:content-transfer-encoding:mime-version; q=dns; s=default; b=hcY
	6idVj1rQop55vWifQPGcaVmloU8jcivRPbROxaEVFmKvVO67blv/i45kdP6n7Y5A
	bwvLHAdivqF+9CCT+Mv6ipDuem7pVjmAOlCl1C0xVCXOSCTw8OLZH47K6I0z5Nyu
	JzinVLDba9RCcrqyO1X0kQ8SRdGJxXtZ4gKh23qM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: mark DOT paulus AT verizon DOT com
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Sudden, unexplained failure of ssh
Date: Thu, 22 Feb 2018 16:56:07 +0000
Message-ID: <60c360a2021449ccbd780c5b51c4db92@OMZP1LUMXCA08.uswin.ad.vzwcorp.com>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Hello,

I've been running 2.9.x under windows 7 on my 16GB laptop for a long time (probably the 
last year), when late last week my ssh outbound quit working.  The failure is indicated with 
this error message:

ssh: Could not resolve hostname csu6220509.vzbi.com: Non-recoverable failure in name resolution

I checked the forums, and what I saw seemed to relate to connecting to VM boxes.
In my case, this is not the cause of the failure.
This machine is my company provided (and software managed) laptop, so I don't have a 
lot of control over (in fact, I don't have hardly any control) what gets "pushed" to it.
However, the one thing that I noticed that seemed to coincide with the failure is that
the company pushed an "Elastica Reach Agent 1.0.20930.0" to my machine.

I thought the issue might have been a version problem, so I updated to the latest 
Cygwin version
$ uname -a
CYGWIN_NT-6.1 TCO10106LKVTAHB 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin

That didn't fix the problem.  I've also tried some other utilities,  which are working, 
such as mobaxterm(Cygwin based), babun(Cygwin based)  and putty.  All those seem to work
fine.

Once I determined that it wasn't my actual network stack, I then tried running ssh under
strace, and now it works.  So, I can use ssh if I use it with strace, but natively by itself
it continues to get the failure in name resolution.

Any clues, hints or pointers on how to go about either determining what the problem is, or 
how to clean it up?

(I am also seeing the same issue with wget, and strace clears that up also
$ wget http://linux1.vzbi.com
--2018-02-22 09:55:38--  http://linux1.vzbi.com/
Resolving linux1.vzbi.com (linux1.vzbi.com)... failed: Non-recoverable failure in name resolution.
wget: unable to resolve host address 'linux1.vzbi.com'

Thanks,

Mark

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple