Re: Supported TLDs
Marco d'Itri writes: > On Jul 08, Simon Josefsson wrote: > >> I don't know the history of inetutils' fork of (g)whois, is there any >> hope in getting these code-bases merged now? Maybe enough water has >> passed under the bridges... > I see no reasons at this point to tie whois to inetnutils development, > since inetutils clearly has failed to become widely adopted, but feel > free to import it again if you want. I'm not sure it is a good idea to do that, do you track copyrightable contributions in any way? Is there any functionality in InetUtils whois that isn't in your version? That is, something added to our fork that didn't go into your version? It is hard to tell from commit history... The situation here is quite unsatisfying and frustrating, but I'm not sure what can be done to improve it. It is similar to our fork of all ancient BSD tools: they are still maintained in FreeBSD/NetBSD/etc but the code have diverged and today there is plenty of features in our tools that doesn't exist in the other versions. /Simon signature.asc Description: PGP signature
Re: Supported TLDs
On Jul 08, Simon Josefsson wrote: > I don't know the history of inetutils' fork of (g)whois, is there any > hope in getting these code-bases merged now? Maybe enough water has > passed under the bridges... I see no reasons at this point to tie whois to inetnutils development, since inetutils clearly has failed to become widely adopted, but feel free to import it again if you want. -- ciao, Marco signature.asc Description: PGP signature
Re: Supported TLDs
Chris Reveles writes: > Hello, > > > I hope 2022 is already up to a good start over there. I am doing some > research and I noticed certain TLDs such as .art and .eth are not resolving > properly from the *whois* command, are such domains on the map to be > supported? Thanks for the report -- I fixed so that .art works, but .eth is not real so I don't see anything to do there. https://git.savannah.gnu.org/cgit/inetutils.git/commit/?id=f7ab99d776fbe7b4fb1bac07b4efb5c882dbcb00 I don't know the history of inetutils' fork of (g)whois, is there any hope in getting these code-bases merged now? Maybe enough water has passed under the bridges... /Simon signature.asc Description: PGP signature
Re: Supported TLDs
On Sun, Jan 09, 2022 at 04:34:07PM -0500, Alfred M. Szmidt wrote: >>I hope 2022 is already up to a good start over there. I am doing >>some research and I noticed certain TLDs such as .art and .eth are >>not resolving properly from the whois command, are such domains on >>the map to be supported? >> >> They are supported, but the TLD list needs updating. Would you like >> to contribut such a patch? whois/tld_serv_list contains all the TLD >> mappings. > >Instead of maintaining a list of WHOIS servers which can easily get >outdated, one could maybe whois query whois.iana.org to know where >to go next: > > A script that could do that would be useful, would you like to give it > a try? Would there be any issues with terms of service or such? I think that list could very easily become stale as new TLDs keep popping up, and registries update DNS names for WHOIS servers, which is why I think instead of generating/embedding such a list in the binary, we should maybe update the logic to do whois all the way from the whois.iana.org in the program, and maintain a local cache with some long TTL, so as to not stress IANA, or other intermediate servers. > > I doubt we would want to run it very often, but just before release > would make sense. -- Ashish | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 "Should I kill myself, or have a cup of coffee?" (Albert Camus) signature.asc Description: PGP signature
Re: Supported TLDs
Hello everyone, Thank you very much for your attention to this matter, I wish I replied earlier, but we are busier than normal over here. My profile may seem fairly technical, but I am more on the management, legal and counseling side, in case the offer on maintaining the project was addressed to me. The reason why I contacted you, is because I consider WHOIS will take a lot of relevance with the increasing activity around domain names(to consider, the massive adoption of domain names by individuals as online identities), as Alfred suggests, taking the reference from IANA may be the best path to keep the tool up-to-date. I wish you success in your projects and be sure you can count with an extra pair of eyes and hands here. Saludos desde México. cR On Sun, Jan 9, 2022 at 9:34 PM Alfred M. Szmidt wrote: >>I hope 2022 is already up to a good start over there. I am doing >>some research and I noticed certain TLDs such as .art and .eth are >>not resolving properly from the whois command, are such domains on >>the map to be supported? >> >> They are supported, but the TLD list needs updating. Would you like >> to contribut such a patch? whois/tld_serv_list contains all the TLD >> mappings. > >Instead of maintaining a list of WHOIS servers which can easily get >outdated, one could maybe whois query whois.iana.org to know where >to go next: > > A script that could do that would be useful, would you like to give it > a try? Would there be any issues with terms of service or such? > > I doubt we would want to run it very often, but just before release > would make sense. >
Re: Supported TLDs
>I hope 2022 is already up to a good start over there. I am doing >some research and I noticed certain TLDs such as .art and .eth are >not resolving properly from the whois command, are such domains on >the map to be supported? > > They are supported, but the TLD list needs updating. Would you like > to contribut such a patch? whois/tld_serv_list contains all the TLD > mappings. Instead of maintaining a list of WHOIS servers which can easily get outdated, one could maybe whois query whois.iana.org to know where to go next: A script that could do that would be useful, would you like to give it a try? Would there be any issues with terms of service or such? I doubt we would want to run it very often, but just before release would make sense.
Re: Supported TLDs
On Sun, Jan 09, 2022 at 05:02:05AM -0500, Alfred M. Szmidt wrote: >I hope 2022 is already up to a good start over there. I am doing >some research and I noticed certain TLDs such as .art and .eth are >not resolving properly from the whois command, are such domains on >the map to be supported? > > They are supported, but the TLD list needs updating. Would you like > to contribut such a patch? whois/tld_serv_list contains all the TLD > mappings. > Instead of maintaining a list of WHOIS servers which can easily get outdated, one could maybe whois query whois.iana.org to know where to go next: == ❯ nc whois.iana.org 43 <
Re: Supported TLDs
On Jan 03, Chris Reveles wrote: > I hope 2022 is already up to a good start over there. I am doing some > research and I noticed certain TLDs such as .art and .eth are not resolving > properly from the *whois* command, are such domains on the map to be > supported? The version of whois in inetutils is a barely maintained fork of a very old version of my package: I recommend that you use mine. Also, .eth is not a real TLD. Absolute falsehood, the whois client in GNU inetutils is maintained. Please report bugs and features to bug-inetutils@gnu.org. Marco, you do not speak for the GNU inetutils project, so please don't say what is or not maintained.
Re: Supported TLDs
I hope 2022 is already up to a good start over there. I am doing some research and I noticed certain TLDs such as .art and .eth are not resolving properly from the whois command, are such domains on the map to be supported? They are supported, but the TLD list needs updating. Would you like to contribut such a patch? whois/tld_serv_list contains all the TLD mappings.
Re: Supported TLDs
Understood, thank you for your prompt response Marco. cR On Sun, Jan 2, 2022, 21:52 Marco d'Itri wrote: > On Jan 03, Chris Reveles wrote: > > > I hope 2022 is already up to a good start over there. I am doing some > > research and I noticed certain TLDs such as .art and .eth are not > resolving > > properly from the *whois* command, are such domains on the map to be > > supported? > The version of whois in inetutils is a barely maintained fork of a very > old version of my package: I recommend that you use mine. > Also, .eth is not a real TLD. > > -- > ciao, > Marco >
Re: Supported TLDs
On Jan 03, Chris Reveles wrote: > I hope 2022 is already up to a good start over there. I am doing some > research and I noticed certain TLDs such as .art and .eth are not resolving > properly from the *whois* command, are such domains on the map to be > supported? The version of whois in inetutils is a barely maintained fork of a very old version of my package: I recommend that you use mine. Also, .eth is not a real TLD. -- ciao, Marco
