While you're correct that this has been discussed in the lists, you're slightly out of context plainly sasying "OpenSRS will not do either one". 1) Yes, it would make sense that the Technical contact would have control over nameserver - but in reality it's the Administrative contact who has authoritative control over the domain name. That is the default system logic. 2) It is your responsability as a company to procure payment from your customers for any transaction. If someone purchases a domain and goes elsewhere - that's a risk of doing business on the internet. You can file legal action against him. We ARE looking at ways of protecting your 'investment' (if you can call it that) - so it's not like "we wont do it", it is - more accurately - "we aren't doing it currently". ... As a solution to BOTH these problems, you *can* (and many resellers have done this) maintain a local database, and backend your system to OpenSRS. Control the passwords to the domain (but still give access to your customers), and you can lock them out completely if they do not pay. We do not force you to use the system as is - it's meant to be tools and frameworks you can rely on to perform the domain registration part of your business. That's pretty much all we do - domain registrations. Charles Daminato TUCOWS Product Manager (ccTLDs) [EMAIL PROTECTED] On Sat, 24 Feb 2001, admin wrote: > You are beating a dead horse. All you need to do is read the archives and > you will find that these issues have been discussed many time and bottom > line is that OpenSRS will not do either one. > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Stein > Sent: Saturday, February 24, 2001 6:02 PM > To: Charles Daminato > Cc: [EMAIL PROTECTED] > Subject: Two Concerns > > > Dear Mr. Daminato and List Members, > > Excuse me if these points have been discussed before, but I am new to the > group. > > Here are two things that really bother me: > > 1) It's crazy that as Technical Contact I cannot even modify the DNS > info. (Unless I happen to know the password) I should not have to ask my > customer to give me their password. If we change our DNS servers, I should > not have to E-mail 500 customers and beg for a password or ask them to make > their own changes. How can we give more control to the Tech Contact? > > 2) We need to be able to suspend an account if someone does not pay their > renewal fee. Although I may pay Tucows for the domain renewal, I need > to be able to prevent my customer from modifying their registration if > they have not paid me for the renewal, or if their check bounces, etc. > > Thank you, > > Michael Stein > Computer House, Inc. > www.computerhouse.com > > > > > >
