interesting, they have a realtime environment where it should make the
updates directly to NSI. since they probably check that the nameservers
are valid.

rm.

On Mon, 20 Nov 2000, Erik Aronesty wrote:

> Except that it takes 3-5 days for the DNS changes to get "implemented" at
> register.com - but they shut off your service immediately.
> 
> We already tried this with an unimportant domain name.  There were 4 days of
> downtime.
> 
> 
> ----- Original Message -----
> From: "ross" <[EMAIL PROTECTED]>
> To: "Erik Aronesty" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Monday, November 20, 2000 12:32 PM
> Subject: Re: register.com in violation of icann policies
> 
> 
> > below you say they will turn off dns if you change your dns
> > provider. yeah, they don't need to run dns for you anymore..... change
> > your dns. and then transfer it away while you aren't reliant on them. if
> > not, just threaten them with a law suit :) no one likes bad publicity.
> >
> > rm.
> >
> > On Mon, 20 Nov 2000, Erik Aronesty wrote:
> >
> > > Dear OpenSRS,
> > >
> > > I want to change to OpenSRS for all my domains - but Register.Com
> > > has threatened to shut us down if we initiate the request.  I sent a
> > > message to ICANN, but they ignored it.
> > >
> > > We have our DNS on their servers, and Register.com will
> > > immediately terminate our DNS services if
> > >
> > >      a) you attempt to initiate a change of registrars or
> > >      b) you attempt to initiate a change of DNS providers
> > >
> > > I don't see any way we can change to OpenSRS without all of our sites
> > > (about 200 of them) going down for weeks while the transfer is going on.
> > >
> > > ICANN should, have a clear, specific policy requiring that the registrar
> > > "unbundle" all secondary domain services during a transfer.
> > >
> > >             - Erik
> > >
> > > P.S. See the message below to the ICANN people
> > >
> > > ----- Original Message -----
> > > From: "Erik Aronesty" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Monday, November 10, 2000 11:01 AM
> > > Subject: register.com's dns policies
> > >
> > >
> > > > I'd like to bring your attention to the abusive policies of one of the
> > > > largest registrars, register.com.
> > > >
> > > > Register.com engages in a technically insidious practice designed to
> > > > frighten people into keeping their domains at register.com.  They have
> > > been
> > > > secretly violating their ICANN agreement (sections II.D.1.b and
> II.D.2.v).
> > > > The fact that nothing has been done about this seems to imply that
> wither
> > > a)
> > > > ICANN does not have the resources to track industry practice of its
> > > largest
> > > > registrars, or b) ICANN is not serious about competitiveness in the
> > > > industry.
> > > >
> > > > ** Register.Com shuts your domain name down for weeks if you try to
> change
> > > > away from them**
> > > >
> > > > Here's how they do this:
> > > >
> > > > Register.com offers free DNS services to people who register their
> domains
> > > > with them.  90% of their substantial customer base take advantage of
> this
> > > > service.  This seems harmless at first.
> > > >
> > > > What they do NOT tell you as part of your registration agreement (or
> > > > anywhere in print), is that Register.com will immediately terminate
> your
> > > DNS
> > > > services if
> > > >
> > > >     a) you attempt to initiate a change of registrars or
> > > >     b) you attempt to initiate a change of DNS providers
> > > >
> > > > Register.Com supervisors have told us that they will not assist us,
> even
> > > if
> > > > we pay them extra to keep our services online during a transfer.
> > > >
> > > > This policy has simply and effectively has prevented us from changing
> > > > registrars (at a savings of about $1000), and I felt that ICANN was
> the
> > > only
> > > > place we could turn to for help.
> > > >
> > > > Please let me know what can be done.
> > > >
> > > >             - Erik Aronesty
> > > >               President
> > > >               Prime Data Corp.
> > > >
> > > >
> > >
> > >
> >
> >
> >
> 
> 

Reply via email to