[27248] in North American Network Operators' Group
Re: identifying ASN
daemon@ATHENA.MIT.EDU (Ryan Tucker)
Thu Feb 10 14:49:49 2000
Date: Thu, 10 Feb 2000 14:14:04 -0500 (EST)
From: Ryan Tucker <rtucker@netacc.net>
To: Mark Kent <mark@noc.mainstreet.net>
Cc: nanog@nanog.org
In-Reply-To: <200002101834.KAA13120@noc.mainstreet.net>
Message-ID: <Pine.BSF.4.21.0002101412270.17424-100000@shell.netacc.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
That happened once with me today... I looked at it funny, showed it to a
couple other folks who also looked at it funny, and then tried again and
it worked. Sounds like some sort of overload condition with an inaccurate
message... -rt
--
Ryan Tucker <rtucker@netacc.net> Unix Systems Administrator
NetAccess, Inc. Phone: +1 716 756-5596
3495 Winton Place, Building E, Suite 265, Rochester NY 14623 www.netacc.net
On Thu, 10 Feb 2000, Mark Kent wrote:
>
> 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?
>
> -mark
>
> P.S. Fortunately, various radb-like entities still list
> information for a lot of ASes.
>
>
>
>
