From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47431@debbugs.gnu.org, hongyi.zhao@gmail.com
Subject: bug#47431: Process Whois connection broken by remote peer.
Date: Sat, 27 Mar 2021 11:01:36 +0000 [thread overview]
Message-ID: <b299646274aa53c1efd0@heytings.org> (raw)
In-Reply-To: <83y2e9nhne.fsf@gnu.org>
>> 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."
>
> We don't use the external 'whois' command, so its man page is not
> relevant, I think.
>
Indeed. Would it not make sense to use the external whois command if it
is available, and to fall back to the Lisp code when it is not?
In any case, the whois-server-tld alist needs to be updated, it has only
15 entries [1], the whois client for GNU/Linux has more than 400 (see
[2]). And these 400 are only for the domain name lookups, there are two
others for IP addresses, another for NIC handles, and another one for AS
numbers...
[1] Its first entry is not a valid server name, all other ones except the
"org" and "mil" are valid server names but are not the appropriate server
for the corresponding TLD.
[2] https://raw.githubusercontent.com/rfc1036/whois/next/tld_serv_list
next prev parent reply other threads:[~2021-03-27 11:01 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
2021-03-27 8:08 ` Eli Zaretskii
2021-03-27 11:01 ` Gregory Heytings [this message]
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=b299646274aa53c1efd0@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).