[27243] in North American Network Operators' Group
Re: identifying ASN
daemon@ATHENA.MIT.EDU (Mark E. Mallett)
Thu Feb 10 13:59:35 2000
From: "Mark E. Mallett" <mem@mv.mv.com>
Message-Id: <200002101851.NAA11038@iridium.mv.net>
To: mark@noc.mainstreet.net (Mark Kent)
Date: Thu, 10 Feb 2000 13:51:41 -0500 (EST)
Cc: nanog@nanog.org
In-Reply-To: <200002101834.KAA13120@noc.mainstreet.net> from "Mark Kent" at Feb 10, 2000 10:34:11 am
Content-Type: text
Errors-To: owner-nanog-outgoing@merit.edu
>
>
> With all this talk of tracing attacks I just noticed that
> whois -h whois.arin.net
> seems to not be as informative as it used to be.
>
> When looking up various ASN I sometimes get the information I want,
> but frequently I get:
>
> Sorry, you shouldn't see this record.
>
> or
>
> No match for ASN "..."
>
> (Sample ASes are 2855, 5400, 9057, 11486)
>
> Did I miss some policy change?
I noticed this a little while ago and reported it to noc@arin.net -
10# host whois.arin.net
whois.arin.net has address 192.149.252.22
whois.arin.net has address 192.149.252.21
My perspective is that the .22 server seems to be messed up, and
that querying the .21 server gets good results.
-mm-
