OpenSRS has been working with this person since this problem initially
occured.
As I stated in my previous email, a slew of domains were transfered over
to OpenSRS that were owned by Tucows. There was well over 300 names - a
list that was compiled by various sources over several years while Tucows
was a few different entities (Tucows was in a partnership with an ISP in
Toronto that has been through different ownership cycles, and Tucows was
affected by such changes).
There was a few names that erroneously on the list - and explanations have
been given to these persons regarding the mistaken request for transfer.
This domain made it into our system and our folks (Mike Nudelman and Karen
Johnston - who handles Compliance issues) have been right on the job to
get this matter fixed.
As for why this domain was transfered - it was a mistake. Hundreds of
emails were sent to a few different individuals in the organization (those
that were tied to the domain in one way or another), and these were
largely run through with little thought - it was strongly believed that
all the domains belonged to us and we acted accordingly.
This individual has been explained this matter several times - and we're
still working to complete the correction. A general inquiry to a list
really isn't warranted - there's no official stance on lists that OpenSRS
staff aren't members of.
As an aside - the administrative/etc contact information for this domain
have already been passed back to this individual. The DNS information
never changed - never affecting the performance of this domain. AND - he
gets free year to boot due to the transfer *grin*
If there are any other questions - let me know :)
BTW - any ICANN accredited association can perform a transfer request via
RRP with no authorization - it is up to the organization to implement a
method to prove ownership prior to transfer, and I strongly believe
OpenSRS has a world class system in place - we've had little complaints
about erroneous transfers, and most of these are results of hacked NSI
Mail-From security models.
"William X. Walsh" wrote:
>
> Here is an update...
>
> This is a forwarded message
> From: Jim Rezzino <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Monday, July 31, 2000, 11:09:52 PM
> Subject: OpenSRS- whos in charge?Part2
>
> ===8<==============Original message text===============
> UPDATED INFORMATION
> Do I have a more credible email address now :)
> This in reference to OpenSRS making a unauthorized Domain transfer.ALL
> information is provided below.Any thought or ideas on the matter?
> May 24,
> To whom it may concern
> Within 24 hours we will be initiating the transfer of your domain to
> OpenSRS. You will be receiving an e-mail regarding this transfer and
> couldyou please reply to that e-mail ASAP and follow the enclosed
> instructions.
> Should you have any questions or concerns, please don't hesitate to
> contactme.
> Regards.
> Michael Nudelman
> Research Analyst - OpenSRS
> May 25,
> To whom it may concern
> Please disregard my previous letter concerning the transfer of
> vcdomains.com. The domain was on my list in error. Please accept my
> apologies for any inconvenience this may have caused you. Should you
> receive any correspondence regarding the transfer, please disregard. You
> domain will not be modified or transferred in any way.
> Regards.
> Michael Nudelman
> Research Analyst - OpenSRS
> June4,
> Domain Name: VCDOMAINS.COM
> Registrar: TUCOWS.COM INC.
> Whois Server: whois.opensrs.net
> Referral URL: www.opensrs.org
> Name Server: NS1.DOMAINREGISTRY.NET
> Name Server: NS2.DOMAINREGISTRY.NET
> Updated Date: 04-jun-2000
>
> July 14 I found out and contacted OpenSRS
>
> To whom it may concern
> We're currently looking into the transfer and a solution for it.
> To expedite the process, could you provide me with the administrative,
> billing and technical contact you would like to have so that we can make
> the appropriate change. Additionally, you have the option of transferring
> the domain back to NSI or leaving it with OpenSRS. Please inform me of
> where you would like the domain transferred to.
> Once again, please accept my apologies for this error.
> Regards.
> Michael Nudelman
> Business Analyst - Business Information
> July 14,
> Thank you for responding so quickly. One problem has arisen, RegisterFree
> doesn't appear to have a transfer area, so we're unable to transfer the
> domain. If you could contact RegisterFree to inquire about transferring
> the domain, this would help the process.
> Michael Nudelman
> Business Analyst - Business Information
>
> July 27,Instead of being returned to the original registrar it went to
> NSI.Now I'm trying to get it transferred back.
>
> Domain Name: VCDOMAINS.COM
> Registrar: NETWORK SOLUTIONS, INC.
> Whois Server: whois.networksolutions.com
> Referral URL: www.networksolutions.com
> Name Server: NS1.DOMAINREGISTRY.NET
> Name Server: NS2.DOMAINREGISTRY.NET
> Updated Date: 27-jul-2000
> I'm still waiting for them to explain how this happened.Any thoughts?
> James Rezzino
>
> ===8<===========End of original message text===========
>
> --
> Best regards,
> William mailto:[EMAIL PROTECTED]
--
Charles Daminato
OpenSRS Support Manager
[EMAIL PROTECTED]
