From: David T Hollis <dhollis@davehollis.com>
To: Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.kernel.org, dev@work.bitmover.com
Subject: Re: [bkbits] predicted outage
Date: Fri, 02 Apr 2004 21:16:26 -0500 [thread overview]
Message-ID: <1080958586.2688.3.camel@dhollis-lnx.kpmg.com> (raw)
In-Reply-To: <200404020218.i322I0GC017257@work.bitmover.com>
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>
prev parent reply other threads:[~2004-04-03 2:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 2:18 Larry McVoy
2004-04-03 2:16 ` David T Hollis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1080958586.2688.3.camel@dhollis-lnx.kpmg.com \
--to=dhollis@davehollis.com \
--cc=dev@work.bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®