Jack,
Thanks for confirming that most NSI employees are still as clueless as
ever. Even some of the things you believe are facts, really are far from
the truth... See my comments below...
> The term "denied" that NSI uses in their emails is actually a passive
> thing meaning do nothing. They do not actually send a "denied transfer"
> to ICANN or any body overseeing the transfer process to allow another
> transfer request to be initiated immediately. You can ONLY wait until
> the request times out. I am not absolutely certain but I believe the
> time-out period is set when a given Registrar signs their agreement with
> Verisign. The time-out is as per the settings of the Registrar
> initiating the transfer request.
Most of the above paragraph is incorrect. (1) If they do not send a deny
to the Verisign Registry, the transfer *will* be approved by
default. (2) The time out period is five days for all
registrars. (3) Transfers are processed by the Verisign Registry. ICANN
has nothing to do with it. Also note that Network Solutions is a Verisign
company.
This is all in black and white in Echibit B of the Registrar License and
Agreement as published at
http://www.verisign-grs.com/registrar/dotcom/forms/NSIRLA-110499.pdf
> If a transfer is denied because the domain is not in a paid up status
> they send a notice to the admin contact to that effect. (Interestingly
> we had many domains transfer successfully prior to NSI's email
> verification policy that expired by as much as 6 weeks!)
Yeah, that was caused by a bug that they finally fixed. I'm amazed that
they actually figured out how to fix a bug.
> If a transfer is denied by NSI not receiving a confirmation email then
> NSI sends an email to this effect to [EMAIL PROTECTED]
>
> In either case it is an almost useless gesture because the domain is
> still locked out from further transfer requests until it times out.
If they do send the denied request, that should free up the domain to
submit the transfer again prior to the five day time out.
> At first I dealt with a front line customer service person who offered
> to ensure that the domain in question was rejected properly so the
> transfer could be resubmitted. I told her that I wasn't willing to do
> this as it was a problem I wanted fixed such that I didn't have to call
> NSI every time a domain transfer wasn't acknowledged within their 3 day
> window. Keep in mind that at this point neither I or this 1st level
> tech support/customer service type realized how these transactions
> worked. (I was mistakenly under the impression that if NSI denied the
> transfer "properly" it would remove it from the "transfer pending"
> pool.) She agreed that she couldn't in fact help me and transferred me
> to 2nd level tech support.
Your impression should be the way it works. If NSI denies the request,
that should free the domain to allow you to submit another transfer
request. If NSI doesn't deny the request, the transfer will happen by
default after the five day period (from experience it appears to be five
business days not calendar days).
> The second person was obviously more knowledgeable and he was the one
> that told me about the there not actually being any method of refusing a
> transfer to have it immediately put back in an "okay to transfer" state.
> I decided to vent a little on this guy because he seemed to be able to
> comprehend what I was talking about.
One more thing, it may still take the Verisign registry a day or so to
clear the domain to be able to request another transfer since it appears
they do not process these transfer e-mails in real-time.
-Bill
