Perhaps something I've mised, but is ARIN.Net no longer handling
lookups? I usually use them to find offending users but got this
when doing a lookup.
No match for 64.124.168.60
I did have the same problem yesterday (Wednesday). Looks like it
is working today. Maybe some leftover bug from
On Thu, 21 Nov 2002, Martin Renschler (EWU) wrote:
tried the link and entered my PacBell home DSL static IP address and was
shocked to see my private name come up behind CustName field! Wrong
Address though.
-snip-
NetRange: 67.116.xxx.xxx - 67.116.xxx.xxx
CIDR: 67.116.xxx.xxx/29
On Thu, 21 Nov 2002, Martin Renschler (EWU) wrote:
:
:tried the link and entered my PacBell home DSL static IP address and was shocked to
:see my private name come up behind CustName field! Wrong Address though.
:
:Isn't this violating privacy rules? Geez!
:/Martin
:(private mail not
--snip--
tried the link and entered my PacBell home DSL static IP address and
was
shocked to see my private name come up behind CustName field! Wrong
Address though.
From http://www.arin.net/library/guidelines/swip.html
When registering residential customers, ARIN recommends the
Hi,
Actually this is what I was also wondering - I thought that half the
time LIRs don't register their assignments? Can anyone confirm this?
Thanks,
Harsha.
I am shocked to see that there is a LIR that actually registers what
they are supposed to (at least according to the RIPE region).
Worked for me:
[mlyon@fitzharris mlyon]$ whois -h whois.arin.net 64.124.168.60
[whois.arin.net]
OrgName:Abovenet Communications, Inc
OrgID: ABVE
NetRange: 64.124.0.0 - 64.125.255.255
CIDR: 64.124.0.0/15
NetName:ABOVENET
NetHandle: NET-64-124-0-0-1
Parent:
Thanks All for the response.
Looks like the web interface (www.arin.net) is the problem.
Thanks again!
