X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=CobV00bDGUF5Vp76
	Zi5a35x/qWTeSZsZxj9hNwKb4+ZdVe0qBsUCbkwCCpPcq3yL+q4bth2ISj1tgmlN
	fGSoxA/ivDFS5Vtb3JvQnLAcBPLlGWosqM99MNu9S4G1sqlE1ZUQR1VyeIwap9wN
	7ZuVnDHj4M+yKILfnrsTklyzpOA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=Z3vzeOKxz5xCGcHygKkmug
	G4jUk=; b=klVUqhoCO+ARNoLar+1w1HT9cIWxHP8A03tRpvkuL4CCySBRGRKyNK
	UA3UQCYEmmGsox/Fh7PyhVykyBmnAMyHrdX5uuzdEK85r3kneWEBQ5rTcLRyo108
	SFCKGiUdHnJ0CVho55gIQ1djTsTFHVCShJn9Vnjy0+65yxsuOSrjg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=4.2 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2 spammy=H*UA:Bat!, H*x:Bat!, H*r:sk:postmas, HTo:U*frank
X-HELO: smtp.ht-systems.ru
Date: Tue, 15 Mar 2016 14:00:38 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <54382838.20160315140038@yandex.ru>
To: Frank Farance <frank AT farance DOT com>, cygwin AT cygwin DOT com
Subject: Re: ctrl-c doesn't reliably kill ping
In-Reply-To: <56E75B3E.7020102@farance.com>
References: <56E6F25A DOT 7070000 AT gmx DOT de> <56E75B3E DOT 7020102 AT farance DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Frank Farance!

> A little digression, so you understand the background ... The workstation I am
> doing this from is connected to a Verizon router to their FIOS network.  Now the
> reason I mention this is that the router's DNS (via DHCP to my workstation) is
> 192.168.1.1, which I presume is forwarded from the router upstream to Verizon's
> DNS caches.  So if I type the URL http://something.that.doesnt.exist in my 
> browser, rather than getting a Hostname Not Found error (at the name resolution
> level), it actually loads up a page saying "something.that.doesnt.exist" isn't
> found and then I have a Yahoo set of search results on things matching the 
> broken hostname.

> So all of this is normal ISP stuff: they actually resolve unknown addresses to
> their own website (which is 90.242.140.21).

This is NOT "normal", this is a violation of protocol.
Whoever encounter such behavior should call their ISP and tell them to stop
doing it.


-- 
With best regards,
Andrey Repin
Tuesday, March 15, 2016 13:59:48

Sorry for my terrible english...


--
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