[144468] in North American Network Operators' Group
Re: Disappointing ARIN - A great advertisement for the USA ?
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Mon Sep 12 13:00:32 2011
In-Reply-To: <Pine.LNX.4.61.1109121251290.18171@soloth.lewis.org>
Date: Mon, 12 Sep 2011 12:58:32 -0400
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Jon Lewis <jlewis@lewis.org>
Cc: ppml@arin.net, NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Mon, Sep 12, 2011 at 12:53 PM, Jon Lewis <jlewis@lewis.org> wrote:
> On Mon, 12 Sep 2011, Eric Krichbaum wrote:
>
>> That was on June 25th according to Mark Kosters. =A0They started to answ=
er
>> with both the parent and delegated objects. =A0That hosed the way RWHOIS
>> data
>> was being reported to most things as the client won't know which to send
>> through to the rwhois servers. =A0Still works from an old SCO box but no=
t
>> from
>> anything current.
>>
>> A "+" flag on the query from some clients will get it to recurse, but fo=
r
>> my
>> tests kicked back "%error 350 Invalid Query Syntax".
>
> Prepending the query with a + "works" for me, in that I get the expected
> data, but there's additional unexpeced data (full record for the Parent,
> even if the Parent is just an ARIN /8) in the output that will probably
> still cause problems for scripts.
my guess is that ARIN is hoping folks turn to the actual RESTful
interface for many scripted purposes...I keep expecting to see some
example python/perl/etc off:
<https://www.arin.net/resources/whoisrws/index.html>
but at least the api is documented, it ought to be fairly
straightforward to make a simple whois client.
(that could be extended to be used in whatever scripty thing you were
using before)
-chris
