IT.COM

GoDaddy Account Push Issues

Spaceship Spaceship
Watch

Soofi

Love Domain NamesTop Member
Impact
6,010
Is anybody facing Godaddy Account Push Issues?

Kindly advise as most of us have been facing trouble while pushing a domain name to another user at GD! :(
 
2
•••
The views expressed on this page by users and staff are their own, not those of NamePros.
1
•••
@convertcontent - I cannot say for sure because it is not me doing the pushing. but from the confused responses from the pushers, to this question, they don't know what they are doing, because GD instructions are so ambiguous.

Actually. I believe GoDaddy have got their knickers in a twist with these pushes. All pushes should be pushed without a fresh 60 day hold, and with the change of whois registrant. Just like every other registrar on the planet.
 
1
•••
1
•••
Select "do not change details" or something similar. There are options to keep DNS records unchange or to use the details from the specified account. Push without changing the details and ask the new owner to change them later.

I think changing the account details later will mean another round of confirmation from old/new owner later? What mess requiring two seperate lots of confirmation, godaddy own tutorial isn't accurate either.
 
1
•••
Not needed actually as the domain is already in the new owner's account so he has full control. This is in my experience.

Remind me never to sell/push a GoDaddy domain to you. I have up to 5 domains at GoDaddy, not in my account, but in someone else's account, who hasn't changed the whois to themselves. It gets really sore that 5 years later these domains still have me as the owner, and GoDaddy remind me every year about renewal. Believe me. I've given up trying to get those domains to change their whois. I've even reported them as wrongful whois. But NOTHING works.
 
Last edited:
1
•••
Don't you think I already give them specific instructions? I do. Do you think anybody pays any attention? Not many. Coupled with the fact the rules for a push keep changing, and GoDaddy's ambiguity. Remember. I'm only accepting a push as a last resort. Which is why there are not many. I don't think it is practical to create a template, with the rules keep changing. I have to create a fresh template for every push. It is just not worth the effort. So my template to the seller, says things like, never accept a push from a GoDaddy email (because that will only guarantee the push takes 5 days and may/will incur another 60 day lock). But they still do it.

Nope. the solution, is for GD to make this push easier. 1 set of rules only. Rules that are not constantly changing. Rules that are clear and are not ambiguous. Where a push is without a fresh 60 day hold, and with the change of whois registrant. Just like every other registrar on the planet.
@stub @Shaun Lun @johnnie018 @sohel momin @lock @convertcontent @infosec3 @bonin @yandig @ozzo @Soofi @maxtra @creataweb @dande @Dave @DnFolk @tonyk2000 @Joe Styler

I do agree, Stub : it should be push easy and no tranferout 60day lock rebeginning. (HOWEVER : I can understand when Godaddy premiumservice said last year to me that if a domain is new and the 60dayout-lock from purchase (registration from new domain) is still not finished, that if a push to you is done, after 20 days of the first registeration purchase that still 40 days are to go, provided that a specific WAY of PUSH is used : there are several possibilities to push they said. And a whole explanation was sent to me.

(Anyhow, concerning this current topic, indeed also I purchased last week a domain here and the PUSH led to problems with seller and contacts, so I could only transfer out from his account with authcode. The seller didn't know what he exactly had to do : After the third time cancelling the push because strange emails came from Godaddy, 2 chats of the seller with Godaddy, and 3 phonecalls of me with Godaddy : I finally said to the Godaddyrepresentant on the phone : sorry : but I don't want trouble with the seller, sorry I'll transfer out this one, this takes too long). Thanks for singalising this problem @Soofi , and starting this thread : I already PM'd the seller this URL-thread.

BUT SOMETHING IS IMPORTANT :!: : About the 60day-lock in better times (so before this mess of the last week), I was told last year by a premiumhelper of Godaddy that after a PUSH has been done the right way so that no 60 day transferoutlock should happen, but the seller missed or used the wrong way to push, or there has been a mistake : You have to mail to the following emailaddress : [email protected] I was told to me that they (the people you arrive at, at this emailaddress), can review the lock and remove it if possible and you can transfer out sooner.(in case of push and changements). If they do it, I don't know, I never was confronted with that since they told me that over the phone).
I hope this is true.
:xf.smile:

(There's also something else, but I'll contact Joe Styler soon about this in PM).
 
Last edited:
1
•••
We rolled out a new change of account last week. The goal was to simplify the process and to change the back end architecture to a new one. The goal was to make it faster and better, but there were a couple things that didn't work right.
The thought was that most customers do not do change of accounts all the time so it should be an easier process where you enter the email address of the person you want to give the domain to. If they have an account with us we let them know. They click accept and you get the email to accept and the domain moves.
The emails didn't work right and that was fixed last week after we rolled this out. There are couple other changes coming shortly that should further make this process smoother and hopefully at the end of the day easier than it had been.
As far as the emails go we have to send some of them. ICANN mandates that we notify the gaining and losing party of the WHOIS when the contacts change. This is a security measure they put in place.
The goal is to get the process easier for a non domain expert to move and accept domains.

Thank you @Joe Styler for the update. We're still experiencing serious issues with almost all internal Godaddy domain transfers and when we forward customers to your support to handle the transfers manually, they are sent back to us.

We now have an increasing number of domains that are completely locked. We can't access the domain as they are in either "pending transfer" or "pending update" while we also can't cancel and re-initiate these transfers.

How do we solve this problem? Can we please get assigned an account manager that moves domains manually for us for the time being? Or is there another solution available?

Kind regards,

Reza
 
1
•••
Thank you @Joe Styler for the update. We're still experiencing serious issues with almost all internal Godaddy domain transfers and when we forward customers to your support to handle the transfers manually, they are sent back to us.

We now have an increasing number of domains that are completely locked. We can't access the domain as they are in either "pending transfer" or "pending update" while we also can't cancel and re-initiate these transfers.

How do we solve this problem? Can we please get assigned an account manager that moves domains manually for us for the time being? Or is there another solution available?

Kind regards,

Reza
We do not have anyone who handles moving domains from accounts. If you send me a domain as an example I am happy to look into what is happening.
Pending transfer means that someone needs to take action, you or the person gaining the domain.
Pending update normally means that someone needs to approve the change of registrant still to the new registrant.
I can tell you exactly what is happening once you send me a domain to look at.
 
1
•••
If you send me the domain I will take a look and see if I can help.
 
1
•••
I am seeing the same, have two names in progress. Transfer out window is blank.
 
1
•••
So my turn to see how this works. Domain sold at Afternic, to be pushed to their Escrow account at GoDaddy. I called my rep, wasn't available, got another rep. They don't even know about the new system. Rep said something about the nameservers option, I told him it wasn't there any more. Just email address, optional customer number and then the option of Yes or No for the contact info. He said pick No, it would be smoother. So we'll see.

@Joe Styler - Do the Reps know about this new way of doing things? VIP reps of all people. It seems like something where you would get them all together for a meeting and go thru it.
Yes they do know about it and there was a meeting. I think two. Also they have a training doc they can access easily that shows the whole process. The issue here is probably that there are two ways to do the COA and each has it's own subpaths. Some people see one and some are using the other. It will all be cleared up to one path soon as they make some other releases in the very near future. They have been continually making them over the past few weeks and the end state will be a single (easier) path.
 
1
•••
Please fix mobile website transfer out, pending changes accept functions.

For years this has driven a lot of people crazy, being out, and trying to push, or accept a push thru mobile device.
 
1
•••
Was just about to ask this.

The verbiage is going to be confusing to some, it should use the old verbiage.

So, I'm guessing selecting Yes will NOT change the domain contact info.

I was just in chat with Escrow and you can get to the old way by going to Domains, checking off domain, hitting More, then selecting Begin Account Change, which will look like the old way of pushing the domain.

I hope this mess is fixed soon.
the fix for the two views was released yesterday as well as some other improvements.
 
1
•••
@Joe Styler
For the last 24 hours a Go Daddy member in Montevideo, Uruguay has been in touch with YOU trying to push a domain to me. She tells me you are trying to work this out. That's great....

She says via email to me that she has tried several times to push the domain to me. Yes, she has received the GD email confirming the contact change and now the domain appears in her outgoing pending area that the domain is in "changing account" status.

A MAJOR PROBLEM - I have received nothing from GD. No change of contact email for me to approve or disapprove. And nothing appears in my incoming pending area. I have checked both "old version" and beta and the results are the same. What am I doing wrong??

Lots and lots of time being wasted on a procedure that used to be easy. Please comment....
 
1
•••
It depends on how the change was started. Right now there are two ways to do it. They are phasing one out within a week. Things should be much smoother after that, meaning the whole process should be easier than it was before. I am sorry there was a problem with this one.
 
1
•••
If you send me the domain I will take a look and see if I can help.
Joe, I thought this would have been resolved by now but I am getting another "Given request is invalid. If you feel this is incorrect please try again" for a new domain name that needs to be pushed to epik account.
 
1
•••
This still isn't a smooth process, it was actually easier back in the day. Haven't done a push in awhile. So:

Transfer/Push to another account:
Input email
Input Customer #
Pick whether or not to keep Contact info, I said no

Wouldn't the simple way just to be able to click Accept Transfer after that Under Transfers?

So buyer is on phone support with GoDaddy because he thinks there are tech issues, before I get a chance to see yet another email that said:

the Review and Approve Update where I had 2 choices:
Choice 1 - Lock domain transfers for 60 days after contact information updates.
Choice 2 - Do not lock domain transfers after contact information updates.

Why can't that be asked when I first push?

So I contact the buyer again to ask which one he wants. Apparently he also gets that email, so we both have to pick the same choice.

It's a push, should be simpler.

It's easier transferring a name to another registrar. I'm always transferring to enom from GoDaddy for names I sell at Namejet.

It's input name, input auth code at enom. Wait a little, then just click accept at GoDaddy.
 
Last edited:
1
•••
Anybody else having 'fun' with godaddy pushes today again?
Decided long ago easier to auth code out then do the push dance.

It used to be so simple, now I dread a Godaddy push.
 
1
•••
I'm done with GoDaddy after all these push issues. How is it I can push something in 1 minute on somewhere like NameCheap, but it takes 3 hours today on GoDaddy?
 
1
•••
0
•••
Select "do not change details" or something similar. There are options to keep DNS records unchange or to use the details from the specified account. Push without changing the details and ask the new owner to change them later.
 
0
•••
Select "do not change details" or something similar. There are options to keep DNS records unchange or to use the details from the specified account. Push without changing the details and ask the new owner to change them later.

I try this a few times, just wondering to update the DNS back to GoDaddy nameservers
 
0
•••
Sorry I mean to say domain contact info in particular. I mentioned DNS but what I meant was the domain (under transaction) 's contact details can be left unchanged. There is also an option to use the contact details of the new owner. Select the former and it's usually done. I have faced this issue in the past too. Push was unsuccessful when selecting "use details from specified account".
 
0
•••
I don't want to change the domain contact details, simply because I'm trying to push the domain to Undeveloped escrow account... and still, don't work. They can't accept the domain every time they getting an error when clicking on the email from GD
 
0
•••
I see. That might be a different case from what I have experience.
 
0
•••
  • The sidebar remains visible by scrolling at a speed relative to the page’s height.
Back