Transfer for .com needing code?

[Spokuz]

Hello

I am unnable to transfer .com domains since RS is now requesting a code, but the other companies do not have it yet, so we cannot transfer the domains.

How can we solve this?

[raman_rb]

Hello

I am unnable to transfer .com domains since RS is now requesting a code, but the other companies do not have it yet, so we cannot transfer the domains.

How can we solve this?

Today we got the same problem.

We have contacted support already and from their response it seems like they are also confused as EV1 interface has BUG which prevents Auth code to be set. We were able to work this out by going to manage.opensrs.net directly and set the auth code there. It worked for us and may work for you. Try it.

Of course, other registrars may have issues and each case should be checked with loosing registrar.

Damn, bad as we had no issues with transfers of .com/.net domains before.
Just .org domains required auth code and it is available at Domain Extras (for EV1/OpenSRS)

Btw, why .com/.net domains got auth code? When this has started officially?

[Spokuz]

raman, were you transfering into resellone or out (to another company)?

[raman_rb]

TO ResellOne FROM EV1/OpenSRS.

Btw, EV1 staff is working on the problem already.

It is NOT problem of ResellOne, but the 'feature/requirement' which has affected all today's transfers of .com/.net I suppose.

[raman_rb]

Advice: contact loosing registrar and ask them to set any auth code for you, then use it for transfers. They should have systems ready as they should register .org domains with auth code.

[kasey]

Yeah... expect com/net transfers to be problematic for the next month or so. VeriSign is mandating that all of its registrars switch over to an EPP-style registry by October 1... and some of them have apparently been taking their sweet time getting ready (i.e. waiting until the last minute).

Tucows and ResellOne both switched over their systems within the last week or two. (With Tucows, there was an announcement... not so much with R1, I just happened to notice the EPP status codes starting to show up on WHOIS queries.)

Now, all that being said... the documentation from Tucows on this says that October 28 is the drop dead date when the auth code will be required for transfers. Up until then, it's supposed to be optional. On the Tucows side, we've been entering "RRP" in the place of the auth code when a registrar isn't providing one for the domain-to-be-transferred yet. That may work on the R1 side as well.

[raman_rb]

Confirmed: you need to use RRP instead of the code in the case loosing registrar has no codes yet. It works!

[xfreelancer]

Yeah right... only at Resellone.

Anywhere else you can transfer domains without this code YET.
Resellone introduced this code way too fast for others.

Here:
verisign.com/Resources/Naming_Services_Resources/Registrar_Connections/page_038962.html#01000005
states that:
"From October 3 through October 28, registrars may use any combination of RRP and EPP subject to the total Auto-Batch Pool limit of four connections per registrar."

So, from October 3. Resellone is requesting that code in september.
Shit, another mistake of Resellone.

[xfreelancer]

Yeah... expect com/net transfers to be problematic for the next month or so. VeriSign is mandating that all of its registrars switch over to an EPP-style registry by October 1... and some of them have apparently been taking their sweet time getting ready (i.e. waiting until the last minute).

Tucows and ResellOne both switched over their systems within the last week or two. (With Tucows, there was an announcement... not so much with R1, I just happened to notice the EPP status codes starting to show up on WHOIS queries.)

Now, all that being said... the documentation from Tucows on this says that October 28 is the drop dead date when the auth code will be required for transfers. Up until then, it's supposed to be optional. On the Tucows side, we've been entering "RRP" in the place of the auth code when a registrar isn't providing one for the domain-to-be-transferred yet. That may work on the R1 side as well.

Where did you got the RRP code ? From the registrar? Or from where ?

[Domains_Aamir]

Hello,

We really regret any failures on our part to make this transition smooth. It was not actually ResellOne who decided to introduce the auth codes early. We truthfully did not have the option to not introduce them.

I am happy to announce that the auth codes should be fully integrated into the system at this point. Everyone's codes for .com and .net auth codes should be automatically generating at this point without complication. Should a problem arise after this post with this issue, please contact support@resellone.net. We should have no problems fixing the issues for you.

Thank you,

Aamir A.
Reseller Services

[xfreelancer]

Sure, but you forgot to say only one little thing.

That today september 9th, all this mambo crap about AUTH code or RRP code it's just your invention...
And I will explain you if you do not understand...

The system with the AUTH code it is not official, and IT IS NOT REQUIRED.

The system with the code seems to be required in October and not September.
So today, actually this whole month, that code it is something that you are requiring your users to type because you really DO NOT CARE ABOUT YOUR USERS.
That's all.

And if you ask yourself why I say all this.. I will explain you also very simple.
If you guys have a domain that expires tomorrow, and the registrar is eNOM, then you might have to buy that domain again from them, because eNOM is telling something quite simple:
"There is no AUTH code required for .COM domains so we cannot give you one"

Clear and simple... it's my situation now, that I have to buy again arround 20 domains just because Resellone asks a code... that this month... it is an invention...

And by the way Resellone, show me WHERE it is written on this big internet that I AM REQUIRED TO TYPE THAT CODE THIS MONTH (again, september).

No problem though... I'm happy buying from eNOM.

[Spokuz]

Again... not working

The error which occurred was:

Could not issue transfer: Unable to process transfer for DOMAIN.com: Authorization error.
The domain you are trying to transfer to WebSP - Comercio e Prestacao de Servicos Informaticos, Lda, an authorized EV1 service provider, may be locked at the current registrar WILD WEST DOMAINS, INC.r, or invalid authorization code is provided. Please contact WILD WEST DOMAINS, INC. to verify and try again.


The code "RRP" no longer works.

What do we do now?

[kasey]

I just logged into one of my client's GoDaddy accounts... there's an option to "Send Auth Info" now on the .com/.net domains.

Unfortunately, the way VeriSign decided to set this up, if both registrars are supporting EPP, you're going to have to have the actual auth code to do the transfer. That's at least been my experience so far...

[paulius]

Wow. I have the same exact issue. I have a domain to transfer and it's asking an auth code.

I'll send an email to ResellOne and see what they can do about it.