RE: [cobalt-users] Forms & SSL [was IP Change]

[<rpaiz@xxxxxxxxxxxxxx>]

> Can you think of any reason the client got the SSL warning
> when they filled out the forms prior to moving over to
> FrontPage?

I cannot. Of course, that's reasonable since I've never actually used an
SSL certificate at all... I've just been trying to learn a little about
them to be prepared for the day (soon) when I will want one. :)

> Strangely, a handful of them resolve through to
> the changed IP site already after just 2-3 hours.

Not so strange. If, for example, your TTL (time-to-live) for DNS is 24
hours, then there are some people out there using DNS servers that last
asked for (and cached) your info about 20-22 hours ago. Those expired
and began resolving correctly almost immediately.

We always just worry about the worst-case scenario: the guy who cached
our DNS info three minutes ago... I should have my new connection
installed next week (YAY!!!), so I've begun knocking down TTL's to one
hour.

Based on advice from this list and your own experience now, by the time
I'm actually ready to move the server to its new home, I'll drop TTL
down to 1 minute about four hours before the move. Then, into the car
and out the door...

I'm also making sure that the primary DNS for the entire operation will
remain unchanged throughout the move, and I'll have someone changing its
name records while I move the server. And I'm doing all this Monday
morning at 4:00am. Hopefully, the world won't even know.

If anyone can think of something else I can do, let me know. :)
Overdoing it? Maybe, but happily so. Target is *still* 99.999% someday,
currently holding internally at 99.985% and 99.850% externally due to
network outages. Must make more money, get bigger pipes, implement
BGP... :)

--
Rodolfo J. Paiz
rpaiz@xxxxxxxxxxxxxx <mailto:rpaiz@xxxxxxxxxxxxxx>