North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
FW: identifying ASN
- From: Marsh, Jerry
- Date: Thu Feb 10 14:47:14 2000
Web to the ARIN WHOIS location and enter: ASN xxxx
> From: Mark E. Mallett[SMTP:firstname.lastname@example.org]
> Sent: Thursday, February 10, 2000 10:51 AM
> To: email@example.com
> Cc: firstname.lastname@example.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 email@example.com -
> 10# host whois.arin.net
> whois.arin.net has address 220.127.116.11
> whois.arin.net has address 18.104.22.168
> My perspective is that the .22 server seems to be messed up, and
> that querying the .21 server gets good results.