On 29 September 2014 08:16, Steve Holdoway <[email protected]> wrote:
> linuxsysadmin.guru (: > I toyed around and found an interesting entry in the bwwhois package: # 2nd-level domains in the .arpa tree .in-addr.arpa whois.iana.org # IP version 4 .ip6.arpa whois.iana.org # IP version 6 .e164.arpa whois.iana.org # E.164 telephone numbers .arpa whois.iana.org # ARPA GTLD Seems those domains are sufficient for resolving the second level whois: jwhois -h whois.iana.org guru | grep whois whois: whois.donuts.co jwhois -h whois.donuts.co jwhois -h whois.donuts.co linuxsysadmin.guru [Querying whois.donuts.co] [whois.donuts.co] Domain Name: linuxsysadmin.guru Domain ID: d6752c8040864ccfb27c4c72d5bf9e9d-D WHOIS Server: http://whois.101domain.com Referral URL: http://101domain.com Updated Date: 2014-02-05T16:00:51Z Creation Date: 2014-02-05T16:00:51Z Registry Expiry Date: 2015-02-05T16:00:51Z Sponsoring Registrar: 101Domain-Inc ltd Sponsoring Registrar IANA ID: 1011 Domain Status: ok Registrant ID: rwe001179c4 Registrant Name: Steve Holdoway <rest snipped> Seems given those two points of information it would be reasonably simple to write a wrapper script that automatically resolved unknown top level whois registries by asking the arpa whois server and doing a top-down whois the same way we do a top-down dns query. Or just ignored the hardcoded file entirely and always did full traces. whois -h whois.iana.org rocks | grep whois: whois: whois.unitedtld.com jwhois -h whois.iana.org zone | grep whois: whois: whois.donuts.co jwhois -h whois.iana.org support | grep whois: whois: whois.donuts.co jwhois -h whois.iana.org name | grep whois: whois: whois.nic.name -- Kent *KENTNL* - https://metacpan.org/author/KENTNL
_______________________________________________ Linux-users mailing list [email protected] http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
