> >a) If the admin contact acks the request, they will put in the wrong
> >reseller's profile for maintenance and re-billing later.
>
> They should not ack a request they do not recognize.
All humans do not always do the right thing.
> >b) If the admin contact does not act the request, and the wrong reseller
> >keeps re-submitting it, the domain can never be pre-registered, and as a
> >result, will come available November 1st. (Maybe this is the goal?)
>
> Ummm, no.
>
> First of all, all existing .ca names will NOT become available 11/01/00.
No, but my comment comes into play for 12/01/00
> Second of all, we can kill the original request and then they can
> register. contact [EMAIL PROTECTED]
This is only if [EMAIL PROTECTED] acts on it. I've had an outstanding
ticket# 45186 since Thursday Oct 12th.
The last thing I heard, is that the domain was registered by another
reseller and that the domain owner should reject that confirmation.
The "48 hour period" has expired, and I just tried submitting it now (Today,
Oct 17th, 5 days later)
Error comes back:
The domain is taken or a request has already been submitted for it
---------
Yesterday, Oct 16th, I sent an e-mail to support regarding this issue, and I
haven't heard back. Here's a sample of what I sent:
> [domain] was pre-registered by another reseller. If the domain
> owner didn't place that order, they should reject the confirmation.
They never received any confirmation.
They are still not found in the CIRA database, so the pre-registration
hasn't taken effect yet.
Please contact the other reseller and ask them why they have [domain] in
their queue? Perhaps they meant to advance-register it?
Once this is released, I will try another pre-registration for my customer.
Thank you.
---------
I figured this might be helpful to diagnose this one in discuss-list for
other RSPs who are experiencing the same thing.
Any ideas Scott?
