Why not a simple catch in the Horizon code that looks for a transfer of a specific domain and dumps out the proper results?
$resellerid-transfer-succeeds.net $resellerid-transfer-fails.com This solves the code testing reliability issues. On Wed, Mar 12, 2003 at 01:18:54PM -0500, Zeljko Dimic wrote: > That is a very good idea, but considering number of resellers, even If > I were to create only 100 domains for each one, I'm afraid that both > Verisign and our OPS dept. would be after me. > > So, without further delays, I started creating domains: > from: test-transfer-tucows0000.com > to: test-transfer-tucows9999.com > > that do not belong to registrar used to operate Horizon environment. > Against these domains you can issue transfer. Transfer will never > complete (due to registry lack of auto-ack feature), and once issued > domain cannot be reused, so these domains are first come, first served :) > > As I write this, be aware that there are only few hundred domaains > created, but processing of all will finish today. > > Z. > > On Wed, 12 Mar 2003, Csongor Fagyal wrote: > > > > > > > > > >Anyway, I've got proposal: As a band aid, would it suffice if I > > >were to create 10K domains eligable for transfers, something like > > >test-transfer-tucows0000..test-transfertucows9999? You'd have to itterate > > >over them to find which one is still elligable for transfer, as once you > > >issue tranfer command against such domain, that one is no good to anyone > > >anymore... We can replenish this list from time to time. > > > > > >Please let me know. > > > > > > > > I would prefer test-transfer-tucows-$resellername-xxxx.com > > > > - Cs. > > > > -- Joe Rhett Chief Geek [EMAIL PROTECTED] ISite Services, Inc.
