• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Main Menu

WHOIS test broken?

Started by cconn, July 18, 2011, 11:10:39 AM

Previous topic - Next topic

cconn

I am failing every whois test, I seem to be doing the same as usual, anyone?

cholzhauer

What input are you giving the test?  Can you provide one thing you submitted that doesn't work?

gnarlymarley

The test works for me.  ARIN changed their output, so I suspect you might want to check out this post: http://www.tunnelbroker.net/forums/index.php?topic=1858.0

k1mu

Quote from: cholzhauer on July 18, 2011, 11:26:04 AM
What input are you giving the test?  Can you provide one thing you submitted that doesn't work?

Anything in the ARIN region fails. For example, let's take devcentral.f5.com, or 2001:19b8:101:2::f5f5:5
a simple WHOIS query (whois 2001:19b8:101:2::f5f5:5 @whois.arin.net) gives:

Quote[Querying whois.arin.net]
[whois.arin.net]
#
# Query terms are ambiguous.  The query is assumed to be:
#     "n 2001:19b8:101:2::f5f5:5"
#
# Use "?" to get help.
#

#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=2001:19b8:101:2::f5f5:5?showDetails=true&showARIN=true
#

American Registry for Internet Numbers ARIN-002 (NET6-2001-1800-0) 2001:1800:: - 2001:19FF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
Tierpoint, LLC TIER6-3 (NET6-2001-19B8-1) 2001:19B8:: - 2001:19B8:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#


So, you can query the network using the handle:

whois "n ! NET6-2001-19B8-1" @whois.arin.net
which gives
Quote[whois.arin.net]
#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;handle=NET6-2001-19B8-1?showDetails=true&showARIN=true
#

NetRange:       2001:19B8:: - 2001:19B8:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
CIDR:           2001:19B8::/32
OriginAS:       AS30340
NetName:        TIER6-3
NetHandle:      NET6-2001-19B8-1
Parent:         NET6-2001-1800-0
NetType:        Direct Allocation
RegDate:        2004-08-12
Updated:        2007-10-25
Ref:            http://whois.arin.net/rest/net/NET6-2001-19B8-1

OrgName:        Tierpoint, LLC
OrgId:          TIERP
Address:        23403 E Mission Ave
City:           Liberty Lake
StateProv:      WA
PostalCode:     99019
Country:        US
RegDate:        2007-10-18
Updated:        2011-04-05
Ref:            http://whois.arin.net/rest/org/TIERP

OrgTechHandle: DSE61-ARIN
OrgTechName:   SELIGER, DAN
OrgTechPhone:  +1-509-688-2575
OrgTechEmail:  dan.seliger@tierpoint.com
OrgTechRef:    http://whois.arin.net/rest/poc/DSE61-ARIN

OrgTechHandle: TNO36-ARIN
OrgTechName:   Tierpoint Network Operations
OrgTechPhone:  +1-509-688-2590
OrgTechEmail:  noc@tierpoint.com
OrgTechRef:    http://whois.arin.net/rest/poc/TNO36-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#

Neither of these WHOIS results work with the HE test. I've just been using other regions.

fredbaker30

I think you dont know how to find whois.... Otherwise its not possible that you are failing .... its such an easy task to perform.. how are you failing what is wrong ? be specific

k1mu

#5
Quote from: fredbaker30 on September 04, 2011, 02:23:57 PM
I think you dont know how to find whois.... Otherwise its not possible that you are failing .... its such an easy task to perform.. how are you failing what is wrong ? be specific

Thanks for the gratuitous insult. Yes, I know how to find whois.  If you had bothered to actually read what I posted rather than just trying to be a stupid jerk, you would have noticed two whois output pages. D'oh.

Yes, it's possible that it's failing.  The test is broken and DOES NOT WORK for entities in the ARIN region due to changes that ARIN made in their WHOIS output.

How I'm failing and what's wrong is detailed above.

Please don't bother to reply unless you have constructive suggestions.

HE, any chance you can get this test working again?  It's getting to be a pain to find whois entries outside the ARIN region (and outside 2a01:238, who seems to be putting up dozens of sites per day..)

pcreager

I came across the same problem, but luckily was almost done with my dailies when it started.  (1500 w00t!  ;D )

Looks like ARIN took it upon themselves to make "improvements":
https://www.arin.net/resources/whoisrws/index.html
https://www.arin.net/resources/whoisrws/whois_diff.html

Since they have better IPv6 adoption across the pond, most of my lookups tended to be in Europe anyway, and hence from RIPE.  

k1mu

Well, this problem will be fixed soon. From ARIN's announcement mailing list:

QuoteARIN announces a pending change to Whois query behavior on port 43.

Prior to 25 June 2011, a query for an IP address in the ARIN region would return with that assignment/allocation within the ARIN region, and a query in the ARIN region for an IP address with no assignment/allocation would result in a "no match" response. On 25 June, a change was misapplied. The intent of this change was to return ARIN's /8 for IP queries within ARIN's region for which there is no assignment/allocation, a behavior meant to align ARIN's Whois output with that of the other RIRs. However, this change introduced an unintended behavior of returning ARIN's /8, in addition to the desired results, in responses where IP addresses had been assigned or allocated.

This change in behavior has created some confusion. On 2 October, ARIN will reinstate the previous behavior for Whois IP queries so that results are returned the way they were before 25 June.

ARIN has provided two examples of a Whois query for reference:

* Query with ARIN's /8 returned in the result set hierarchy:
https://www.arin.net/announcements/2011/20110919.html#example1

* Query without ARIN's /8 returned in the result set:
https://www.arin.net/announcements/2011/20110919.html#example2

Whois-RWS behavior will not change as it was not affected by the configuration change made on 25 June.

We apologize for any confusion this has caused.

Regards,
Mark Kosters
Chief Technical Officer
American Registry for Internet Numbers (ARIN)

pcreager

Sure seems like it took them a while to realize they broke WHOIS lookups for a lot of folks.

jimb

There was a pretty big flame-thread in the NANOG list about this, with the president of the ARIN even getting involved.  :)

pcreager

Quote from: jimb on September 24, 2011, 01:13:46 PM
There was a pretty big flame-thread in the NANOG list about this, with the president of the ARIN even getting involved.  :)
Got a link?  Sounds like entertaining reading.   ;D

jimb

#11
Quote from: pcreager on September 24, 2011, 09:59:10 PM
Quote from: jimb on September 24, 2011, 01:13:46 PM
There was a pretty big flame-thread in the NANOG list about this, with the president of the ARIN even getting involved.  :)
Got a link?  Sounds like entertaining reading.   ;D
http://mailman.nanog.org/pipermail/nanog/

I'm pretty sure this is the thread: http://mailman.nanog.org/pipermail/nanog/2011-September/039958.html

It's an entertaining, and sometimes informative list.   :P

tykimus

Hello guys,

Sorry for the delay in responding.
Please retest WHOIS and email us at ipv6@he.net if you see any other issues.

Thanks!