I can think of at least one scenario that makes sense - someone registers a
name and then sells and transfers it to someone else, without passing along
the RSP information. Since whois returns only the registrar and not the
RSP, there is no way to determine who the RSP is without contacting OpenSRS.
It would be nice to have RSP contact information in the whois record (this
is not the highest item on my wish list, but it is on there).
This will likely become more of an issue as time goes on. When someone
registers a domain name for ten years, I always wonder if there is any
chance they will remember where they registered it, and if their email
address will be the same, when it comes up for renewal. (I also wonder if
we will still be using domain names at all in ten years!)
----- Original Message -----
From: "Charles Daminato" <[EMAIL PROTECTED]>
To: "WebWiz" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, December 06, 2000 8:26 AM
Subject: Re: Nameserver changes
There's a problem with this logic. Support will inform the customer to
notify his/her RSP to get that information - that's our MO. The customer
will have to explain firstly that they do not know their RSP (this is
rather dubious - you can't remember who you gave money to for a service?),
and then there will be some fax-in-proof type procedure (not 100% sure of
what's current, it's been a few months since I was deep in support).
Our staff will likely contact the actual RSP to ensure they are aware of
what's going on with these transactions - by design we do not send
username/password information to the end user ourself. It's a function
that only the RSP has, as only the RSP SHOULD have it. If this customer
still owes money to his current provider (hence his sudden amnesia) we
will leave things as is and let them work it out as they should.
Charles Daminato
TUCOWS Product Manager (ccTLDs)
[EMAIL PROTECTED]
On Tue, 5 Dec 2000, WebWiz wrote:
> I take it your customer doesn't know his username and password either...
>
> Send an email to [EMAIL PROTECTED] and ask them to send the
> username/password to the admin contact for the domain. If your client
isn't
> that person or can't talk with that person, then that should set off
warning
> bells in your head!
>
> Once your customer receives the email, he/she can change the nameservers
> easily or create a subuser account for you to make the changes.
>
> Regards,
> Eric Longman
> Atl-Connect Internet Services
>
> +-------------------------------------------------------+
> | Atl-Connect Internet Services http://www.atlcon.net |
> | 3600 Dallas Hwy Ste 230-288 770 590-0888 |
> | Marietta, GA 30064-1685 [EMAIL PROTECTED] |
> +-------------------------------------------------------+
>
> ----- Original Message -----
> From: "Kevin Javaheri" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, December 05, 2000 8:25 PM
> Subject: Nameserver changes
>
>
> Hello all,
>
> I have a customer with a domain name that was registered by some RSP, he
> is not sure who the RSP is, and he wants to change the name servers to
> point to us. The registration record shows Tucows, Inc. and
> whois.opensrs.net,
> however, we do not know how to make these modifications. Since the
customer
> is the registered owner of the domain name, is there any way he can
> authorize
> a name server transfer directly to OpenSRS?
>
> Thank you,
>
> Kevin Javaheri
> SiteTurn Networks
> [EMAIL PROTECTED]
>
>
>
>
