Join Date: Mar 2009
Posts: 21
|
01-24-2012, 01:40 PM
|
First of all, Hello to Tigger, Brent and my other old friends that might still be here! (Sorry, I haven't read through the forums at this point to get caught up.)
I've been totally mainstream for a while now, and stopped doing client work last year with one exception being my favorite Italian restaurant.
I used to get great advice from members here, so thought I'd give it a shot for this one.
Here's the issue:
My client's former employee that registered their domain name, did so in his own name and in his Go Daddy account that he has control over. He left on bad terms and is refusing to transfer the domain to their company account at Go Daddy.
My inclination is that they should file a UDRP Complaint for Cybersquatting.
However, I am unsure if that is the right thing to do because at present their site functions fine. The DNS is pointed correctly, etc. However, he still has control over the domain, and if he wanted to, could re-direct it.
We have another variation on the name, not as good, but still the name of the business.
Another idea I have is to make the other domain the functioning one, and 301 re-direct the current one to it while the DNS is still pointed to the hosting I have control over.
The current domain with live site that is registered in the disgruntled employee's name:
GratzziGrille.com
The alternate name, which currently re-directs to above, but I am thinking of reversing this:
GratzziItalianGrille.com
Gratzzi Italian Grille is the actual name of the restaurant, but we felt it was better to use the shorter domain and re-direct the longer one for type-ins, until this issue came up.
|