[27247] in North American Network Operators' Group
FW: identifying ASN
daemon@ATHENA.MIT.EDU (Marsh, Jerry)
Thu Feb 10 14:43:09 2000
Message-ID: <0B6CB38AD203D311BBD70001FA7E3944EA97EE@OSCMAIL02>
From: "Marsh, Jerry" <MarshJ@WSDOT.WA.GOV>
To: "'nanog@merit.edu'" <nanog@merit.edu>
Date: Thu, 10 Feb 2000 11:14:35 -0800
MIME-Version: 1.0
Content-Type: text/plain
Errors-To: owner-nanog-outgoing@merit.edu
Web to the ARIN WHOIS location and enter: ASN xxxx
> ----------
> From: Mark E. Mallett[SMTP:mem@mv.mv.com]
> Sent: Thursday, February 10, 2000 10:51 AM
> To: mark@noc.mainstreet.net
> Cc: nanog@nanog.org
> Subject: Re: identifying ASN
>
>
> >
> >
> > 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-
>
