Debian Bug report logs - #774603
[wishlist] support iana.org style redirects

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Anand Kumria <wildfire@progsoc.org>

To: submit@bugs.debian.org

Subject: [wishlist] support iana.org style redirects

Date: Mon, 5 Jan 2015 12:17:26 +1100

[Message part 1 (text/plain, inline)]

Package: whois
Version: 5.1.1

Hi,

The IANA whois server (whois.iana.org) will issue referrals to all known
domains, whether they are existing gTLDs, ccTLDs or the newer
(whois.nic.<domain>).

However, like the DNS, it is not authoritative and simply issues redirects.

It would be nice if whois supported the redirection format -- roughly
".*refer: ([^ ])+$".

Thanks,
Anand

[Message part 2 (text/html, inline)]

Message #10 received at 774603@bugs.debian.org (full text, mbox, reply):

From: md@Linux.IT (Marco d'Itri)

To: Anand Kumria <wildfire@progsoc.org>, 774603@bugs.debian.org

Subject: Re: Bug#774603: [wishlist] support iana.org style redirects

Date: Mon, 5 Jan 2015 04:07:03 +0100

[Message part 1 (text/plain, inline)]

On Jan 05, Anand Kumria <wildfire@progsoc.org> wrote:

> The IANA whois server (whois.iana.org) will issue referrals to all known
> domains, whether they are existing gTLDs, ccTLDs or the newer
> (whois.nic.<domain>).
I am not sure of which problem this would solve, can you elaborate?
There is no point in using this as the default since my own database has 
an higher quality than the IANA one.

-- 
ciao,
Marco

[Message part 2 (application/pgp-signature, inline)]

Message #15 received at 774603@bugs.debian.org (full text, mbox, reply):

From: Anand Kumria <wildfire@progsoc.org>

To: "Marco d'Itri" <md@linux.it>

Cc: 774603@bugs.debian.org

Subject: Re: Bug#774603: [wishlist] support iana.org style redirects

Date: Sat, 10 Jan 2015 16:23:17 +1100

[Message part 1 (text/plain, inline)]

Hi Marco,

The problem that I believe implementing this will solve is one of updates.

For example, today I wanted to check an entry in the .bar domain; I am
using a downstream distribution (in my case Linux Mint 17.1), and it has
whois 5.1.1

That version does not know that .bar is a domain, and where it should be
queried. That version is from Jan 2014, and you updated the file in Apr
2014 (
https://github.com/rfc1036/whois/commit/171705cbde06ef350f2e34ae76070a41a681c35f
).

It will probably be a year or more, until the first downstream (Ubuntu in
this case) and then the next downstream (Linux Mint) get an updated version
that does know about the domain.

Which is a shame, since you've put in a lot of time and effort maintaining
whois. A naive user would believe that the program is at fault.

If you implemented this new feature (checking whois.iana.org for
referrals), my immediate problem will not be solved but it will mean that
for future LTS distributions where updates are incorporated only after a
tedious amount of time then whois will "Just Work" with newly delegated
domains.

I still think you should consult your internal database first, just have
IANA's whois as a fallback.

Hope that clears up why I think this would be a nice-to-have feature.

Thanks,
Anand





On 5 January 2015 at 14:07, Marco d'Itri <md@linux.it> wrote:

> On Jan 05, Anand Kumria <wildfire@progsoc.org> wrote:
>
> > The IANA whois server (whois.iana.org) will issue referrals to all known
> > domains, whether they are existing gTLDs, ccTLDs or the newer
> > (whois.nic.<domain>).
> I am not sure of which problem this would solve, can you elaborate?
> There is no point in using this as the default since my own database has
> an higher quality than the IANA one.
>
> --
> ciao,
> Marco
>

[Message part 2 (text/html, inline)]

Message #20 received at 774603@bugs.debian.org (full text, mbox, reply):

From: Marco d'Itri <md@linux.it>

To: Anand Kumria <wildfire@progsoc.org>, 774603@bugs.debian.org

Subject: Re: Bug#774603: [wishlist] support iana.org style redirects

Date: Sun, 11 Jan 2015 19:43:05 +0100

[Message part 1 (text/plain, inline)]

On Jan 10, Anand Kumria <wildfire@progsoc.org> wrote:

> I still think you should consult your internal database first, just have
> IANA's whois as a fallback.
I am considering parsing the referral field, but as a design decision 
this program will never query a fallback server when it does not know 
about a specific resource.
So I am not sure that this would solve your problem.

Debian stable has regular backports (which can also be installed on 
oldstable), I suggest that you require the same quality from other 
vendors as well.

-- 
ciao,
Marco

[Message part 2 (application/pgp-signature, inline)]

Message #25 received at 774603-close@bugs.debian.org (full text, mbox, reply):

From: Marco d'Itri <md@linux.it>

To: 774603-close@bugs.debian.org

Subject: Bug#774603: fixed in whois 5.5.0

Date: Fri, 19 Jul 2019 09:51:43 +0000

Source: whois
Source-Version: 5.5.0

We believe that the bug you reported is fixed in the latest version of
whois, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 774603@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marco d'Itri <md@linux.it> (supplier of updated whois package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 19 Jul 2019 11:31:42 +0200
Source: whois
Architecture: source
Version: 5.5.0
Distribution: unstable
Urgency: medium
Maintainer: Marco d'Itri <md@linux.it>
Changed-By: Marco d'Itri <md@linux.it>
Closes: 774603 931244 931336
Changes:
 whois (5.5.0) unstable; urgency=medium
 .
   * Implemented the -I option to query whois.iana.org and use its referrals.
     (Closes: #774603)
   * Updated one or more translations. (Closes: #931336, #931244)
   * Automatically generate the version string sent to servers because I
     kept forgetting to update it with new releases.
   * Updated the .zm TLD server.
   * Added new recovered IPv4 allocations.
Checksums-Sha1:
 c1ce8f7a6c041bf07450ecd3b2d584abe5f7142f 1317 whois_5.5.0.dsc
 9eab12389783e5ceca8c3833b2fdbb9038b37e98 85600 whois_5.5.0.tar.xz
 743e4c6d6b1792418dbcbddc5abb67d91fc32af5 5616 whois_5.5.0_amd64.buildinfo
Checksums-Sha256:
 07067d913f1e84119e61ebd54bb3bcf42417ccc45d0c5138a0f0c58808fe1c30 1317 whois_5.5.0.dsc
 64ec63339d7ad559cd6722bd3141a1e5787817bd921841a813ee17a0a34b6f3d 85600 whois_5.5.0.tar.xz
 2ed518b5972cf7520f1ce6e786a0584c09887f64addec77e307349ef66e010d2 5616 whois_5.5.0_amd64.buildinfo
Files:
 2b2d879f7064aa95af45a59b26e83cb4 1317 net standard whois_5.5.0.dsc
 768c57ad06bd2014d1a6ca5b8bd61636 85600 net standard whois_5.5.0.tar.xz
 b084b4377376d08a6f24267c3acf038d 5616 net standard whois_5.5.0_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQGzBAEBCgAdFiEEGBsIcS5ipP0URKfyK/WlwSLE96QFAl0xjj0ACgkQK/WlwSLE
96SMMwwAv6GyEDb4P/KdIa2YhmHxkXXImqlHYQpE2HByfyDPe1WvJ6TsGxLyPagw
KS76hFQASj1UBdYEyAQQosYKBN1d+BkUuK0nnAJmf/kovyobWpcTx5CoSsg/vzks
TYBOfWvnPO5dY8kGlhNC7HyHiWwFtQaRcy+ZykYE7G9/ZLJDJsgafm/M1Liy5I+g
x8Y7jwgiLsHGBteWuMvTPtS7ettEeffk77IVhiKZpjiLLJZr/Gszb3zJjzZ+W9x6
QAtS45OfNPC/VKxV3gE2wGxMwq1BJ1BkOitN/Gl7SnijtfTg+J1XSeHQ+O2/KjyS
AoZa4CzOW4E4QYxt8vAeFeoa2QNVvmS4FarJFemYFr6RFuYm5lhlWWAIsuhrX0jR
6OWnAUc3Jw7CCtZgaNy0ywj/iiDqKyDc+a7hArxmzVbjMicorYE9cM3id31e3I4Q
7i46pbSh/fnspjeluhnXwYu4BT9mMXYktxVTiVeyoSBy5De59KMre3swYMrnu1kS
JYTtA3eY
=BI5o
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.