I am not coder extraordinaire. But I think you are right on the money with
adding a delay between queries. ( IE: sleep 1, lets say )
If anything it diminishes your chances of getting the "Exceeded Query
Limit" message back from one of the WHOIS servers ( mainly
whois.crsnic.net )
Again, I reiterate that I am not a coding guru ;)~
erol M
On Wed, 29 Aug 2001, Adam Kujawski wrote:
> My employer currently provides DNS service for 250+ domains, most of which
> are NOT yet registered through OpenSRS. As the domains approach expiration, I
> would like to have our customers transfer them to OpenSRS. However, this
> requires knowing in advance when the domains will expire so we can start
> the whole transfer process with the customer.
>
> I'm using Net::ParseWhois in a script to query the WHOIS databases for all
> of the domains and return the expiration date. This is working pretty
> well. However, I have some questons:
>
> If I run this script on a daily basis, for 250+ domains, am I going to
> piss off the WHOIS servers - namely whois.crsnic.net? I don't want to get
> blackholed. I realize that 250 WHOIS queries/day isn't anything compared
> to what SPAMMERS and Registrars generate, but 250+ queries fired off one
> after another may be seen as an annoyance. Should I insert delays between
> the queries to lighten the load, and/or run it only weekly, or just not
> worry about it?
>
> Eventually, I would like to have a system like the SnapShot service
> offered by snapnames.com ($0.50/domain). However, I don't want to reinvent
> the wheel if I don't have to. Does anybody have such a system in place
> that they are willing to share?
>
> Thanks,
> Adam
>
>
> Adam Kujawski [EMAIL PROTECTED]
> Network Administrator Cell: 419.261.3268
> Amplex Internet Services Office: 419.833.3635
>
---------------------------------------
-erol
I don't speak for anybody but myself - that's enough trouble.wq
