There's another side to this... You cannot "force" yourself to be the Administrative contact. The Registrant must agree to have you as the Administrative contact, and even then you're only empowered (as the Admin contact) to administratively handle the domain. You are not allowed to "steal" the domain away from someone for non-payment (they must still be listed as the legal registrant).
Charles Daminato TUCOWS Product Manager [EMAIL PROTECTED] On Mon, 4 Nov 2002 [EMAIL PROTECTED] wrote: > I hate to say it, but your best bet is to: > 1. Have someone else handle EVERYTHING, like an affiliate. > 2. Have your OWN merchant account, and try to hold onto that money with > dear life. Of course, credit card agreements tend to insist you must give > the money back. You have to treat this as a perishable item though. > > As to the admin contact? I have been thinking about forcing myself as the > admin contact that for ANOTHER reason. One person nearly threatened to > sue me because ****HE**** setup his bos as the owner of a domain. Because > of this, he sent me a LENGTHY letter and asked ME to change it, even though > only he could. > > Ironically, THE main domain was in the grace period! Could I have changed > the details even if I owned it? > > Steve > > BTW, My processor *****INSISTED***** that they could NOT give me auth/capture. > People at tucows suggested I charge/void and then charge. That is foolhardy. > Sometimes CC issuers decline on a WHIM! It has happened to me perhaps > 6 times with my card(and NOT because of bad credit or over limit). Ironically, > the processor FORCED me, without telling me, to have auth/capture later. > > The benefit of auth capture is that auth makes the credit card company COMMIT > to the charge! It is THEIR responsibility. After tucows tells you what > you bought, you can capture that portion. > > > Return-Path: > <[EMAIL PROTECTED]> > Received: > from www.opensrs.org (216.40.33.61) by mail.san.yahoo.com > (6.5.029) id 3DC6379C0004BBC9; Mon, 4 Nov 2002 16:26:08 > -0800 > Received: > (from majordomo@localhost) by www.opensrs.org (8.9.3/8.9.3) > id TAA09618 for discuss-list-outgoing; Mon, 4 Nov 2002 19:21:14 > -0500 > Received: > from toronto.mail.tucows.com (toronto.mail.tucows.com >[207.136.98.42]) > by www.opensrs.org (8.9.3/8.9.3) with ESMTP id > TAA09613 for <[EMAIL PROTECTED]>; Mon, 4 Nov 2002 > 19:21:13 -0500 > Received: > from catalyst.tucows.com ([207.136.98.115]) by >toronto.mail.tucows.com > with esmtp (Exim 3.36 #3) id 188rAH-0003V5-00; Mon, > 04 Nov 2002 19:01:53 -0500 > Received: > from chuck (helo=localhost) by catalyst.tucows.com with > local-esmtp (Exim 3.34 #1 (Debian)) id 188rAH-000450-00; Mon, 04 Nov > 2002 19:01:53 -0500 > Date: > Mon, 4 Nov 2002 19:01:53 -0500 (EST) > From: > Charles Daminato <[EMAIL PROTECTED]> > To: > "John T. Jarrett" <[EMAIL PROTECTED]> > CC: > [EMAIL PROTECTED] > Subject: > Re: Changing Admin Info after Refund > In-Reply-To: > <[EMAIL PROTECTED]> > Message-ID: > <[EMAIL PROTECTED]> > MIME-Version: > 1.0 > Content-Type: > TEXT/PLAIN; charset=US-ASCII > Sender: > [EMAIL PROTECTED] > Precedence: > bulk > X-Mozilla-Status: > 0000 > X-Mozilla-Status2: > 00000000 > X-UIDL: > 108122 > > > > > There's no specific link, per se... you can read the Registrar > Agreements with ICANN, but I can give you the gist. > > The domain belongs to the registrant (and is controllable by > whomever they list as Administrative Contact). Period. Only > they can authorize changes to the domain contact information. > > ICANN makes no distinction between "paid", or "unpaid" or "charge > back" or "fraud". Part of the agreements state you must acquire > payment prior to creating the domain (i.e. pre-paid model, as we > employ). > > Now, this isn't much help to you guys (we realize that). > > You can work with Compliance to place the domain name on HOLD, > which will make the domain not work and possibly get the woman to > contact you. It will also prevent transfers so she can't run away > to someone else. If there's a dispute over ownership, we can > assist (but, ideally - with any transaction - it's something you > should sort out yourself). > > Charles Daminato > TUCOWS Product Manager > [EMAIL PROTECTED] > > On Mon, 4 Nov 2002, John T. Jarrett wrote: > > > > > Paul over in compliance says it is against ICANN reg's for > > me to change admin info after a customer refunds on the > > domain name registration: > > > > "I hate to tell you this but you are not allowed to change > > the whois information - ICANN rules. It appears as though > > you are trying to take away someone else's property." > > > > Frankly, I couldn't care less how it looks. I've offered the > > refund codes from the merchant account holder LinkPoint > > themselves so there's proof behind appearances. > > > > Can y'all point me to what he's talking to? I can't find it > > in the UDRP or the Reg Agreement. I don't mind complying > > with written rules if I can find them, but I'd rather not > > let this woman steal three domain name registrations if I > > don't have to! > > > > Thanks, > > John > > [EMAIL PROTECTED] > > > > > > > >
