I did try guessing names at the time.  I sent Tucows a list of 200
something names I had tried, and nothing worked. I requested a valid list
of domains I could test transfers with.  I was given a list of 4 or so.
I tried each of them, and they all returned failure.  

That ticket remains open to this day, unless they closed it silently.  I've
never seen a closure and it has never been answered.

On Sat, Mar 08, 2003 at 01:45:07AM +0200, Doytchin Spiridonov wrote:
> Hello,
> 
> Why don't you just guess some names? Here are 4 examples, if you can't:
> 
> 1. jhgdwhgdw.wejhgd - bad domain name
> 2. jkhgdehg.com - not registered (so can't be transferred)
> 3. abc.com - transfer in progress (so can't be transferred)
> 4. try.com - can be transferred (so try this one; after your transfer
> request is submitted it will fall in case 3, so you should find
> another one for future testing)
> 
> Best regards,
> Doytchin Spiridonov        mailto:[EMAIL PROTECTED]
> http://www.WebYou.com  Web Design and Development
> 
> 
> ---
> Saturday, March 08, 2003, 12:52:45 AM, you wrote:
> 
> J> Just FYI I've been complaining to Tucows about this since ... Jan 2000?
> J> Something like that.  They don't seem to care much.
> 
> J> On Sat, Mar 01, 2003 at 11:26:08PM +0000, Chris Andrews wrote:
> >> 
> >> Hi,
> >> 
> >> I'm trying to test the code I've written against the OpenSRS Perl client.
> >> Everything's fine but transfers: I can't find a set of domains which I can
> >> reliably use to check the various states a domain could be in.
> >> 
> >> Specifically I need a domain for which transfers are OK, and which I can
> >> initiate a transfer on. I don't expect anything to actually happen, just
> >> for the OpenSRS system to check and accept my request.
> >> 
> >> It'd be really useful if there was a set of domains with known states and
> >> results against which code could be tested.
> >> 
> >> 
> >> Chris.
> 

-- 
Joe Rhett                                                      Chief Geek
[EMAIL PROTECTED]                                      ISite Services, Inc.

Reply via email to