Thanks for the warning. :)
I'll make sure this process is included in our fine print somewhere.
So far, the only customers for whom it has been necessary don't know
how to read WHOIS data anyway. ;)
On Thu, Jun 28, 2001 at 11:35:49AM -0400, Charles Daminato wrote:
>
> As long as you're making the registrant aware that you're placing yourself
> as the Admin contact and will be changing their nameservers, this is an
> acceptable practice. If you don't have that *somewhere* (contract,
> byline, fine print) on your site during the order process in a manner that
> the registrant can agree to those terms, you could get in big poopoo ;)
>
> Charles Daminato
> TUCOWS Product Manager
> [EMAIL PROTECTED]
>
> On Wed, 27 Jun 2001, Paul Chvostek wrote:
>
> >
> > We solve this by including our [EMAIL PROTECTED] address as the admin's
> > email address for the transfer. Once the domain is properly transferred,
> > with proper name servers, we can log in and fix the email address.
> >
> > For the customers who initiate changes themselves, it's not our problem.
> >
> > On Wed, Jun 27, 2001 at 02:16:33PM -0400, Jo Shea - Danjo Creations wrote:
> > >
> > > Are there any plans in the works to have new registrations go through with
> > > nameservers as customers enter them? We register domains for non-hosting
> > > customers all the time, and I have a bad habit of being too quick to click
> > > that register button and forgetting to first modify the nameservers to those
> > > they gave us... so they get registered with ours and we look stupid having
> > > to ask them to change them later :o(
> > >
> > > Jo Shea
> > > Danjo Creations
> >
> > --
> > Paul Chvostek <[EMAIL PROTECTED]>
> > Operations / Development / Abuse / Whatever vox: +1 416 598-0000
> > IT Canada http://www.it.ca/
> >
> >
--
Paul Chvostek <[EMAIL PROTECTED]>
Operations / Development / Abuse / Whatever vox: +1 416 598-0000
IT Canada http://www.it.ca/
