This is the mail archive of the
mailing list for the Cygwin project.
Re: ctrl-c doesn't reliably kill ping
- From: Adam Dinwoodie <adam at dinwoodie dot org>
- To: cygwin at cygwin dot com
- Date: Tue, 15 Mar 2016 11:43:17 +0000
- Subject: Re: ctrl-c doesn't reliably kill ping
- Authentication-results: sourceware.org; auth=none
- References: <56E6F25A dot 7070000 at gmx dot de> <56E75B3E dot 7020102 at farance dot com> <54382838 dot 20160315140038 at yandex dot ru>
On Tue, Mar 15, 2016 at 02:00:38PM +0300, Andrey Repin wrote:
> 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 220.127.116.11).
> 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.
It's both normal and a violation of protocol -- a lot of DNS servers,
will replace an NXDOMAIN response will "hijack" the query and return
something that punts the user onto a search page with advertising.
Regardless of how (non-)compliant the system's DNS servers are with the
relevant RFCs, ping's behaviour should never be to hang in the way Frank
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple