North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: High volume WHOIS queries

  • From: Hannigan, Martin
  • Date: Tue Mar 01 09:44:38 2005

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]On Behalf Of
> Paul G
> Sent: Tuesday, March 01, 2005 9:22 AM
> To: [email protected]
> Subject: Re: High volume WHOIS queries
> 
> 
> 
> 
> ----- Original Message ----- 
> From: "Hannigan, Martin" <[email protected]>
> To: "Paul G" <[email protected]>; <[email protected]>
> Sent: Tuesday, March 01, 2005 9:17 AM
> Subject: RE: High volume WHOIS queries
> 
> 
> 
> 
> >> -----Original Message-----
> >> From: [email protected] 
> [mailto:[email protected]]On Behalf Of
> >> Paul G
> >> Sent: Tuesday, March 01, 2005 5:03 AM
> >> To: [email protected]
> >> Subject: Re: High volume WHOIS queries
> 
> --- snip ---
> 
> >> point - they're trying to restrict the practicality of 
> >> attempting to harvest
> >> the data and an open to the public whois server with no 
> >> access restrictions
> >> would defeat that. 
> 
> > I don't know that this is the case, I suspect it's
> > resource management. If the database is getting 
> > slaughtered by applications on uncontrolled auto pilot,
> > it's unusable for the rest of us.
> 
> well, the OP quoted a portion of the aup that requires bulk
> whois data recipients to take measures to prevent harvesting,
> so i presume that arin does care about that and, in fact, that
> consideration is likely the reason they declined to permit the
> OP to run *his own* whoisd off of his *local* copy of the data.

The AUP also says for "internet operational or research
purposes only." Maybe they don't consider the use to fit
in the defintion?

There's an easier fix, IMO. Run a two stage query, 50
and 50, and then append the second 50 to the bottom of
the first.

-M<

-M<