PDA

View Full Version : Transfer Authorization Code fails


buri
04-25-2008, 04:26 AM
Hello,

I am trying to transfer a domain name (urizone.net) from ResellOne to Dotster. Dotster is requesting a Transfer Authorization Code.

I login in at resellers.resellone.net/manage/ and look up the "Domain Auth Code" under "Domain Extras". I copy and paste this code at Dotster. Dotster returns an error saying "The authorization code format was invalid. If you do not have your authorization code, please contact your current registrar to acquire it. Each domain name has its own authorization code." I also tried changing the code to a different value on ResellOne, but none of the values I enter are accepted at Dotster.

Is something on the ResellOne side preventing the transfer? Or is this something I need to troubleshoot on the Dotster side?

Thanks for any help,
BU

Resellone-Eddie P
11-14-2008, 06:17 PM
There isn't any problem that I am aware of specific to our system although I have heard of this sort of thing happening before in terms of general transfer problems. If this problem persists, please let us know.

domains@theplanet.com

Thank you,
Eddie P.
Reseller Services

JamesC
12-09-2008, 02:58 PM
Hello,

I am trying to transfer a domain name (urizone.net) from ResellOne to Dotster. Dotster is requesting a Transfer Authorization Code.

I login in at resellers.resellone.net/manage/ and look up the "Domain Auth Code" under "Domain Extras". I copy and paste this code at Dotster. Dotster returns an error saying "The authorization code format was invalid. If you do not have your authorization code, please contact your current registrar to acquire it. Each domain name has its own authorization code." I also tried changing the code to a different value on ResellOne, but none of the values I enter are accepted at Dotster.

Is something on the ResellOne side preventing the transfer? Or is this something I need to troubleshoot on the Dotster side?

Thanks for any help,
BU
Sorry for taking so long to post this hint had to look back and see what we did the last time this happened to us. (well over a year ago) ;)


You can prevent this from happening by saving the Auth Code that is listed before you use it. After a couple of hours (not sure why it takes this long) you can then use the code with no issues.

This error does not accure often but when it does we have noticed taking these steps seems to prevent the error.

Hope this helps