Trapped at GoDaddy?

[-db-]

First off, let me say I have nothing against GoDaddy. However, the majority of my names are not registered there, and I'm trying to simplify my life by moving all my names to one place.

So, I tried to transfer a couple names that I recently bought from other domainers, but I get a notification saying the names can't be transferred out of GoDaddy because they were moved from one GoDaddy account to another within the past 60 days. And of course, they were indeed moved because ownership change.

The names are set to expire before 60 days is up, so it appears I will be forced to renew at GoDaddy.

This is crazy. It's not the normal "registered within 60 days" rule that all registrars have. These names have been registered since 2002. This appears to be a GoDaddy imposed rule of their own making and design.

Am I missing something? Am I really stuck? No way around it?

 

[William9]

… they were .US domains.

Great.
Are the domains unlocked?
Has GD proved the auth-info code?

 

[Dave_Z]

Well, how about this.....

Both the old owner (who the name was purchased from) and the new owner contact them to verify that everything is legitimate, and even provide some sort of extra proof if they request. Do you guys think they should let domains be transferred away then?

I'm not asking if they will. I'm just asking if they should, in your opinion.

P.S. - Hey there William. In regards to your question, they were .US domains.

I doubt it. Go Daddy tends to stick to their policies like glue.

One weird thing is that one of their resellers I recently got acquainted with
claims Go Daddy didn't impose this on her. I asked her for specifics and I am
just waiting for her reply.

I'll keep you guys posted.

 

[-db-]

William, yes, at the time of the attempted transfers the domains were unlocked, and the .US auth-codes were retrieved from GoDaddy and provided to the new registrar.

Davezan, that's interesting. Please update us if she gives you more details.

I also want to say again, that I've had no bad experiences with GoDaddy in the past and have nothing against them. I just wanted to eliminate some of the many accounts I have at various registrars and get all my domains under one roof. I'm just trying to simplify my own records.

Thanks again to everybody for your valued opinions and feedback.

 

[AdoptableDomains]

The GD policy was probably well meant, but gives them the nice secondary effect of getting lots of names renewed instead of transferred. If the policy was truly only for security, they could offer a paper based way to confirm a transfer out that could override this policy, or do a confirmation with the prior owner of the validity of the ownership change.

 

[EbookLover]

The rule sucks for me ...
I know it's for our own protection, but when I want to sell a domain I regged for less than a month it sucks when I have to wait for another month!

I suggest you read the TOS of any site before you buy anything from them. If you don't it is your own fault, not theirs.

To the OP of this thread...

Did you ever call them on the phone and ask questions? Perhaps there is a way for you to bypass the rule but you'll never know until you look for the answer from the horses mouth instead of specualtive members of NP who really have no clout and no say over GD policy.

 

[Grrilla]

at the time of the attempted transfers the domains were unlocked, and the .US auth-codes were retrieved from GoDaddy and provided to the new registrar.

I had a recent experience w/ Gddy where I was attempting a mass exodus of .info, .biz and .us names to another registrar and had failures on approx 70 names. re: incorrect security codes. http://www.namepros.com/showthread.php?t=59212&highlight=transfer
I had copy/pasted all codes directly off of the Gddy emails, so there was little room for error, particularly an error of this magnitude. It was interesting, that some, but not all of the .com and .net names also failed to transfer. re: Regisrant did not respond to email. Well, there were never any emails sent to respond to. I made a second attempt w/ the same AUTH codes w/ similar results, although this time, a few made it through. On my third attempt, I got smart, and only attempted to transfer one through. I requested an AUTH code, (which showed up w/ different #'s than the first) and re-initiated. Guess what? It also failed. I immediately re-initiated transfer, and this time it went through. Thereafter, all of the names (excluding about 15 that I was forced to renew w/ Gddy, because they had reached or were dangerously close to reaching expiration) went through w/o a hitch. Still haven't figured out the mechanics of this ordeal.

I suggest you read the TOS of any site before you buy anything from them. If you don't it is your own fault, not theirs.

This is all well and good when you are registering a new name and dealing directly w/ a registrar. A problem arrises when you have accepted the TOA w/ a B/O service and, therefore, by proxy, are agreeing to the TOS of a registrar partner and you have no way of knowing who that might be, or what what particulars their TOA might contain or what their operating procedures, may be.

Over the past year, I was succesful w/ 50 or so B/O's, and as a result, have approx 30 different registrars that I am dealing with. These registrars have also been the source of most of my name management problems. On one particular day, I had 8 successful B/O's w/ Pool. Of those 8, 5 names ended up w/ misc. registrars and 3 w/ Namescout. 2 of the names registered w/ Namescout ended up in *seperate* Namescout accts, (the reason why registrars create seperate accounts, by name, for the same user, continues to mystify me), and the 3rd- http://www.lcdtv.biz - although registered w/ Namescout, is on Pool servers, (where the name resolves to a Pool page as a directory w/ affiliate links), and the DNS can't be managed through the registrar, (Namescout). Of the 5 misc registrar names, some can be managed directly through the registrar and are on their DNS, while others are on Pool or Namescout DNS and the registrar of record only "manages" change requests after they have been submitted by email to Pool or to Namescout, depending on what DNS the name happens to be on. Sound confusing to you? Try unraveling this mess from scratch, as I have been doing over the past 2 months.
A sampling of recent email responses to inquiries I have made:

[example].com has not been added to our servers however. You will have to contact Pool.com about this domain name

Pool.Com has asked us to ask you to send your unlock request via email
to
[email protected] or by calling +1.613.768.5140.

And I haven't even gotten to Snapnames, who, inexplicably forwarded outdated contact info, including an email that has been defunct for over a year, to a pair of registrars who successfully made some recent snaps for me. And yes, all contact, as well as billing info was updated several months ago.

Attached please find the documents needed to change the listed email
for a domain name.

Best regards,
Nicmaster

<YOUR PRE-PRINTED LETTERHEAD>


Thu Mar 17 19:15:03 2005

To: G + D International LLC
Domain Processing Center
175 W. Ikea Kai Place
Kihei, HI 96753
U.S.
FAX +1 808 891 8439

Re: Contact Email Change

To whom it may concern:

I hereby give irrevocable authorization to change the listed contact email for the following contact.
I am aware that this change will effect the domain(s) listed below:

Michael:
The domain is not located on our servers.
You can make updates to a domain listed by you by visiting our
Makechanges site at http://register.secureservice.net
If the listed email is invalid, please select 'listed email invalid, update by
fax' in step1.
When the email has been updated, you can make all other changes
online, including replacing nameservers/hosting providers.
Regards,
Support
1stdomain.net

Michael:
I do not know who operates these nameservers, we are a domain
registrar, listing submitted domain information. You may check what
you originally submitted if you ordered a name through snapnames.
Regards,
Support
1stdomain.net

Hope this doesn't come across totally as a vent. (Which, in part, it is). I have slowly, but surely been resolving these issues, and they are about to become a thing of the past. I hope that this exposition of some of my own exploits into the world of name management, (and unneccesarily wasted time), will be of help to someone else facing similar issues/probs down the line. Little did I know about the adventures I would be encountering, after several of my B/Os were succesfully filled, my credit card was charged and the names were to become "mine".

 

[Greg Hal]

This is why I'm not particularly fond of GD for more than a few domains at a time (2-5).

 

[marisolblue]

Godaddys interface is pretty confusing. It seems to take 3-4 clicks to get anything done. But the prices are very good