unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47431@debbugs.gnu.org, Hongyi Zhao <hongyi.zhao@gmail.com>
Subject: bug#47431: Process Whois connection broken by remote peer.
Date: Sat, 27 Mar 2021 07:23:20 +0000	[thread overview]
Message-ID: <b299646274818503158d@heytings.org> (raw)
In-Reply-To: <835z1dp0qg.fsf@gnu.org>


>> On Ubuntu 20.04, I'm using the self compiled git master version of 
>> Emacs. It seems that the whois client in Emacs only works for some 
>> specific domain names, for example gnu.org and emacs.org, but for 
>> others like facebook.com it just hangs and returns nothing. The 
>> following command will trigger the error:
>>
>> "M-x RET whois RET facebook.com"
>
> It doesn't hang here (I'm not on Ubuntu, though).  It times out:
>
>  open-network-stream: make client process failed: Connection timed out, 
> :name, Whois, :buffer, *Whois*, :host, rs.internic.net, :service, 43, 
> :nowait, nil, :tls-parameters, nil, :coding, nil
>
> If I try a different server, it does work:
>
>  C-u M-x whois RET facebook.com RET whois.crsnic.net RET
>
> This returns immediately with a large *Whois* buffer.
>
> Perhaps some network expert could tell why we use by default a server 
> that is less useful.
>

(I'm not a network expert, but...)

It is probably better to let the whois client select the appropriate 
server itself.  The current default whois-server-name (rs.internic.net) 
doesn't work at all, and although whois-guess-server is t, it doesn't work 
well.

The manpage of whois says: "This version of the whois client tries to 
guess the right server to ask for the specified object. If no guess can be 
made it will connect to whois.networksolutions.com for NIC handles or 
whois.arin.net for IPv4 addresses and network names."





  reply	other threads:[~2021-03-27  7:23 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27  1:39 bug#47431: Process Whois connection broken by remote peer Hongyi Zhao
2021-03-27  6:30 ` Eli Zaretskii
2021-03-27  7:23   ` Gregory Heytings [this message]
2021-03-27  8:08     ` Eli Zaretskii
2021-03-27 11:01       ` Gregory Heytings
2021-03-27 11:04         ` Gregory Heytings
2021-03-28 15:39         ` Lars Ingebrigtsen
2021-03-28 20:23           ` Gregory Heytings
2021-03-29  0:19             ` Hongyi Zhao
2021-03-29  4:50             ` Eli Zaretskii
2021-03-29  7:35               ` Gregory Heytings
2021-03-29  8:38                 ` Eli Zaretskii
2021-03-29 11:31                   ` Gregory Heytings
2021-03-29 12:02                     ` Eli Zaretskii
2021-03-29 12:12                       ` Gregory Heytings
2021-03-29 14:16                         ` Hongyi Zhao
2021-03-29 10:58             ` Lars Ingebrigtsen
2021-03-29 11:20               ` Gregory Heytings
2021-03-29 12:19                 ` Gregory Heytings
2021-03-30 13:22                   ` Lars Ingebrigtsen
2021-03-31  7:53                     ` Gregory Heytings
2021-03-31 13:39                       ` Lars Ingebrigtsen
2021-03-31 14:27                         ` Gregory Heytings
2021-04-14 14:55                           ` Stefan Kangas
2022-06-28 13:40                           ` Lars Ingebrigtsen
2022-07-28 10:35                             ` Lars Ingebrigtsen
2022-07-28 21:56                               ` Gregory Heytings
2022-07-29 11:34                                 ` Lars Ingebrigtsen
2021-03-27  9:50   ` Hongyi Zhao
2021-03-27  9:57   ` Hongyi Zhao
2021-03-27 10:33     ` Eli Zaretskii
2021-03-27 12:29       ` Hongyi Zhao
2021-03-27 13:44         ` Eli Zaretskii
2021-03-28  1:41           ` Hongyi Zhao
2021-03-28  6:38             ` Eli Zaretskii
2021-03-28  7:12               ` Hongyi Zhao
2021-03-28 14:11                 ` Lars Ingebrigtsen
2021-03-28 14:15                   ` Eli Zaretskii
2021-03-28 14:19                     ` Lars Ingebrigtsen
2021-03-28 14:55                       ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b299646274818503158d@heytings.org \
    --to=gregory@heytings.org \
    --cc=47431@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=hongyi.zhao@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).