Charles Daminato wrote:
>
> When we originally designed the system we assumed (incorrectly it seems)
> that the Registrant and Administrative contact would be the same, yes, you
> can change this after the fact. However, the API allows you to set all 4
> contacts differently if you wish (not using reg_system.cgi, or a modified
> reg_system). We're working to alter our order logic so a different
> registrant and administrative contact can be specified at order time (via
> the scripts, and the reseller interface).
That's fine. If I can set myself as the admin contact through the API
I'll be happy, currently I cannot. The "Domain Order Edit Form" dosen't
even list the admin contact.
> But the fact of the matter is, the Registrant OWNS the domain, and gives
> control of it to the Administrative contact - by definition from the ICANN
> contracts and in line with how other Registrars work. The Reg/Admin can
> be the same person, or the Admin is someone the Registrant has APPROVED to
> be in control of the domain.
I never said that it should be different. I'm simply sying that the
owner has given me complete authority over the domain, and I should be
able to state that fact when I register the domain.
If I want to transfer an OpenSRS registered domain for one of *MY*
customers to a different registrar for whatever reason, I should be able
to do it without involving the client who will only be confused by email
from OpenSRS (an entity they don't even know about).
I left joker.com because they continued to send renewal notifications
directly to the owner. The owners had no clue who joker.com/CSL was and
this caused alot of unecessary email support. I send *MY* clients
renewal notices, and they renew through me. Please tell me I'm not
going to have the same problem with OpenSRS in a year?
Regards,
Doug
> Something like that...
>
> Charles Daminato
> TUCOWS Product Manager
> [EMAIL PROTECTED]
>
> On Sun, 17 Jun 2001, Doug Sisk wrote:
>
> > This is just an asinine policy!
> >
> > All it does is create work for the RSP. It obviously wasn't originally
> > intended to work that way - why would you even define an admin contact
> > in the api if you were never going to allow RSP's to set it.
> >
> > All this policy accomplishes is now I have to login as my customer and
> > change the admin contact to myself for EVERY domain I register. No
> > other registrars I've dealt with have ever required that. All it does is
> > waste my time. I signed on to OpenSRS because I believe in open source
> > solutions and you guys had the best API (not the best prices). I'm
> > seriously considering going somewhere else and using a proprietary API
> > which at least allows for me to set the admin contact.
> >
> > The owner is always free to login, change their password and the admin
> > contact. The information is not secret, they can see who is the admin
> > contact and change it if they wish. I can't speak for other RSPs but I
> > run a web hosting business. My customers don't know diddly squat about
> > domain names, name servers, registrars, etc. That's what they pay me for
> > - To manage their web site. To do that, I need complete control. If I
> > add a new nameserver I'd like to be able to add it to all my registered
> > domains at once.
> >
> > You guys need to wake up. In most cases the registrant doesn't know
> > anything about Tucows or OpenSRS and they don't want to. That's the
> > whole point of having resellers.
> >
> > Am I alone in my opinion? If so I'll just accept it and go away.
> >
> > Regards,
> > Doug
> >
> > Charles Daminato wrote:
> > >
> > > By definition the owner (Registrant) is the only one who can assign an
> > > Administrative contact other than themselves, with the intention that they
> > > trust the other party and can easily contact them - this means RSPs can't
> > > "put themself" as the Admin contact without the Registrant's permission
> > > (so the owner, in effect, has control over the domain)
> > >
> > > Charles Daminato
> > > TUCOWS Product Manager
> > > [EMAIL PROTECTED]
> > >
> > > On Sat, 16 Jun 2001, Dave Warren wrote:
> > >
> > > >
> > > > And if the technical contact notices a lame delegation, then the technical
> > > > contact can A) Log in and change/remove that nameserver, or B) Do nothing?
> > > >
> > > > How about the owner... Shouldn't the owner have any control over the domain?
> > > > At least in terms of password recovery?
> > > >
> > > > ----- Original Message -----
> > > > From: "Charles Daminato" <[EMAIL PROTECTED]>
> > > > To: <[EMAIL PROTECTED]>
> > > > Cc: <[EMAIL PROTECTED]>
> > > > Sent: Saturday, June 16, 2001 8:59 AM
> > > > Subject: Re: Send the password to owner and billing contact
> > > >
> > > >
> > > > > The billin contact is responsible to ensure the domain is paid for, and
> > > > > only that. The technical contact is responsible for answering any
> > > > > technical questions regarding the domain and that it is not lame
> > > > > delegated, not really much more.
> > > >
> > > >
> > > > ========================================================
> > > > Dave Warren,
> > > > Email: [EMAIL PROTECTED]
> > > > Priority: [EMAIL PROTECTED]
> > > > ========================================================
> > > >
> > > >
> > > >
> >
