Just for our own edification, WHO is the REAL registrar causing these problems?(I
mean is it godaddy, enom, directi, srsplus, etc....)?

Steve

>-- Original Message --
>From: "Gordon Hudson" <[EMAIL PROTECTED]>
>To: "OPENSRS Discuss List" <[EMAIL PROTECTED]>
>Subject: OT: Problems with another registrar
>Date: Mon, 23 Feb 2004 13:55:31 -0000
>
>
>Whilst people complain about some aspects of the Tucows service I bet Tucows
>woudl never do this:
>
>A customer registered a domain name through us in 2001.
>We registered it through another registrar (not Tucows)
>The domain was actually the name of his company followed by .com
>
>In 2002 a major public company set up a chain of shops with the same name
>as our customers company and tried to buy his domain name from him.
>He declined as he had ben using that business name for 10 years.
>
>The company then does various things to "persuade" him to give up the domain
>name
>and he declines to back down.
>Nothing further is heard from them for over a year.
>
>Fast forward to this week.
>The customers web site stops working and on investigation there are no
name
>servers listed for it.
>The whois details have been changed to those of the registrar.
>
>Apparently they got a letter from a lawyer representing the company who
>wants the domain name accusing them of permitting cybersquatting.
>The issue has not been through the UDRP and our customer has received no
>such letter.
>
>So we are no left with a domain that doesn't work and a registrar (ICANN
>Accredited) who appears not to follow the UDRP or even contact the
>registrant before removing them as registrant of the domain name.
>
>No mater what problems may surface with Tucows from time to time i think
>that they have considerably more integrity than many other registrars and
>defintely the one we are dealing with in this case.
>I just couldn't imagine Tucows dowing something like this - ever.
>
>Regards
>
>Gordon Hudson
>Hostroute.com Ltd
>www.hostroute.net
>
>
>
>
>------------------------------------------------
>
>


Reply via email to