There is no downtime.
Change your nameservers while the registration is still at register.com.
(Make sure you have the name servers set up and tested before doing this.)
Wait until the new nameservers are in the zone files, and are receiving
queries for the domains in question. Then change registrars. The name
servers do not change when the domain name is transferred to the new
registrar. (But there is nothing to prevent the losing registrar from
deleting the lost domain names from their name servers and other services.
Just make sure you aren't still using their services when you leave!)
No problem.
----- Original Message -----
From: "Erik Aronesty" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, November 20, 2000 1:19 PM
Subject: Re: register.com in violation of icann policies
This solution would be OK if downtime was an acceptable option. But global
downtime is not an option in today's marketplace.
a) TTL does nothing for new users - we sign up 500 new users each day.
b) our ASP services provide a 99.5% uptime guarantee
c) downtime of 24 hours could cost our firm hundreds of thousands of
dollars in refunds
d) we can't afford to damage our firms reputation as a reliable provider
We maintain 8 servers in 3 countries on this domain name - just to ensure
24x7 uptime on the web site.
Also, I can't believe that even 7 hours of downtime is "acceptable" to the
policymakers at ICANN.
- Erik
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "Erik Aronesty" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, November 20, 2000 1:30 PM
Subject: Re: register.com in violation of icann policies
>
> Hi Erik,
>
> From the looks of it, any course you persue will have some downtime.
> But it needen't be weeks.
> You need to do some forward planning here. I assume the IP's that you
> have will not change, only where the dns info is coming from.
>
> So here's what you do:
>
> 1) Setup DNS somewhere else.
> 2) Add all your domains to that dns & test.
> 3) Do a dns transfer for all your domains. NOT a domain transfer. Here's
> why. A dns change takes about 7 hours to get propogated through the root
> servers. While a transfer can take over a week, during which time
> register.com WILL hose your DNS.
> 4) Once dns has switched over, do a domain transfer.
>
> IF the IP's are the same, you should experience no down-time at all,
> especially if the TTL is set to high enough. Though register.com probably
> has a low ttl, in which case your downtime at most will be a few hours.
>
> Alex
>
> Erik Aronesty writes:
>
> > 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.
> > >
> > >
> >
> >
>
>
> Alexey Zilber
> DAYAK
> Need to register or transfer a domain?
> www.dayak.com charges only $15/year.
> 40 megs of hosting space? $10!
>
