[bkbits] predicted outage

[bkbits] predicted outage

[Larry McVoy]

We're moving office space in about 10 days.  We expect one of our T1 lines
to be switched to the new office as of April 9th.  If that works, then we'll
move all the hardware to the new office and flip the routes to that T1 from
the old T1.  Sounds simple and since the new ISP is the old ISP it might 
actually work (Hah.  Like anything goes that smoothly).  On the other hand,
it might not go great and there might be some time where bkbits.net is not
off the air but it might be at a different IP address.  And DNS takes a 
while to time out.

As we get closer, I will remind you approximately 48 hours and 24 hours 
before the move so those of you who need to sync can sync and not be
disturbed.  If you want more status than that, let me know.

--lm

Re: [bkbits] predicted outage

[David T Hollis]

On Thu, 2004-04-01 at 18:18 -0800, Larry McVoy wrote:

> We're moving office space in about 10 days.  We expect one of our T1 lines
> to be switched to the new office as of April 9th.  If that works, then we'll
> move all the hardware to the new office and flip the routes to that T1 from
> the old T1.  Sounds simple and since the new ISP is the old ISP it might 
> actually work (Hah.  Like anything goes that smoothly).  On the other hand,
> it might not go great and there might be some time where bkbits.net is not
> off the air but it might be at a different IP address.  And DNS takes a 
> while to time out.

Hopefully not point out the obvious, but since you have the lead time,
you could set the TTLs on the DNS entries pretty low (say 5 minutes or
so) now so by the time the changeover is happening, it's fully
propagated.  This way, if you do wind up with the different IP address
scenario, just make the DNS change and it will propagate within minutes
and most folks will never notice.  Once everything is stable again, you
can run the TTL back up.  

A quick check shows that www.bkbits.net has it's TTL set to 86400 (1
day) which means other servers will cache that for up to a day and with
multiple levels of DNS, that can wind up taking awhile to expire.  Bring
that down and things should go smoothly.

Just a thought....

-- 
David T Hollis <dhollis@davehollis.com>