Ah, I see what you mean. You're looking to do a snap-back type of thing, monitoring deletions in the hopes of grabbing domains shortly after they're released.
I think the general concensus, reached December 19-21 2001 on this list, was that the bulk of the RSPs objected to Tucows devoting resources to development of services to facilitate that type of thing. The only other thing I can think of is trying a normal bulk registration, in pending mode so you don't actually request the registrations. A single bulk registration attempt would offload to Tucows the task of checking each domain through the API, and any domains which didn't end up as part of the batch you would know are as yet unavailable. Once domains were successfully pended, you could either process registrations and transfer ownership out of the batch to a unique profile, or kill the entry in your pending queue after notifying whoever's interested. Of course, if I were OpenSRS, I wouldn't take kindly to thousands upon thousands of registration attempts that were known to be likely to fail. If you go ahead with something like this through OpenSRS, I suggest you contact your sales rep to find out if any special relationship needs to be set up so that you aren't labelled an abuser. (If you're paying for the extra resources you're using, I suspect they wouldn't object.) This is really a topic for dev-list. p On Sun, Sep 08, 2002 at 09:29:09PM +0300, Ramy Nabil wrote: > > Thanks Paul, > But the API allows only to check one domain at a time, which will consume a lot of >bandwidth to check > several hundreds (or may be thousands) of domains daily. > I think no need to do DNS queries as the lists wanted to be checked are obtained >from comparing the root > zone files to extract dropped domains, so the domains are not found in the root zone >files and so sure > they will not resolve. > > Best Regards, > > Ramy Nabil > ----- > http://www.mydomreg.com > > Paul Chvostek wrote: > > > On Sun, Sep 08, 2002 at 12:25:43PM +0300, Ramy Nabil wrote: > > > > > > Is there any method to make bulk domain availability check that's it to check >the availability of > > > several domains in one step and get the result as available list and unavailable >one rather than > > > checking them one by one to save bandwidth of both sides. > > > That is required mainly to extract the expired domains list from the dropped >domains. > > > Any suggestions? > > > > You could always write one.� Communication with Tucows via the API > > doesn't take that much bandwidth.� If you wanted to reduce the actual > > checks for availability, you could do quick DNS queries on the domain > > list first, then only check availability for the domains that failed the > > DNS check (since the others are obviously registered and therefore > > unavailable). > > > > Something like this would be pretty simple to code.� If you'd like some > > custom development work done, I'm sure a number of the folks here > > (myself included) would be willing and able to help. -- Paul Chvostek <[EMAIL PROTECTED]> Operations / Abuse / Whatever +1 416 598-0000 it.canada - hosting and development http://www.it.ca/
