Multiple IPs- controlling which one remote sites see[SOLVED]
I'm writing an app that performs whois requests on various servers. Right now it's just a simple whois client; no looping, no multiple requests. Instead of an answer, Network Solution's server (.com, .net) gives me:
> Welcome to the Network Solutions Registrar WHOIS Server.
The IP address from which you have visited the Network Solutions Registrar WHOIS database is contained within a list of IP addresses that may have failed to abide by Network Solutions' WHOIS policy. Failure to abide by this policy can adversely impact our systems and servers, preventing the processing of other WHOIS requests.
If you feel that you have received this message in error, please contact us at:
whoisquery@networksolutions.com and include the following information:Whois Query: test.com
YOUR IP address is 67.18.92.0
Date and Time of Query: Sun Aug 10 11:30:14 EDT 2008
Reason Code: CB
This is the first time I've hit their server from my linode, so I'm guessing my 67.* address was blacklisted from some prior incident. From the error message, it appears they're blocking an entire class C?
I've emailed Netsol asking to be un-blacklisted, but in the meantime, is there a way to change my setup so remote sites see my 69.* address instead? Hopefully that one isn't on any lists.
3 Replies
Have you done many queries to Netsol's WHOIS servers for test.com during your testing? Beware that someone actually owns test.com, and enough of the same query makes them think you're doing data mining, which is against their usage policy.
Quoted from a random query directly to their WHOIS server:
NOTICE AND TERMS OF USE: You are not authorized to access or query our WHOIS
database through the use of high-volume, automated, electronic processes. The
Data in Network Solutions' WHOIS database is provided by Network Solutions for information
purposes only, and to assist persons in obtaining information about or related
to a domain name registration record. Network Solutions does not guarantee its accuracy.
By submitting a WHOIS query, you agree to abide by the following terms of use:
You agree that you may use this Data only for lawful purposes and that under no
circumstances will you use this Data to: (1) allow, enable, or otherwise support
the transmission of mass unsolicited, commercial advertising or solicitations
via e-mail, telephone, or facsimile; or (2) enable high volume, automated,
electronic processes that apply to Network Solutions (or its computer systems). The
compilation, repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of Network Solutions. You agree not to use
high-volume, automated, electronic processes to access or query the WHOIS
database. Network Solutions reserves the right to terminate your access to the WHOIS
database in its sole discretion, including without limitation, for excessive
querying of the WHOIS database or for failure to otherwise abide by this policy.
Network Solutions reserves the right to modify these terms at any time.
@NeonNero:
I doubt they were blocking 67.; one of my Linodes has one of the IPs as 67.18.92.145 (primary IP address), and a WHOIS query just now on a domain I know to be registered via Netsol wasn't blocked. I didn't mean to suggest they were blocking all of 67.. The error message gave 67.18.92.0 as the requesting address, so I figured they were blocking 67.18.92.* (a class C block). I guess they're not though, if your queries went through. Maybe it's just me.
> Have you done many queries to Netsol's WHOIS servers for test.com during your testing? Beware that someone actually owns test.com, and enough of the same query makes them think you're doing data mining, which is against their usage policy.
I ran about 5 queries, even the very first of which was blocked. All better now that I've switched addresses, though.