I've thought about this for a while.
I have a friend in another part of the country that has done this for me
when I know my connection is going to be down for a while.
For short periods of time, email can handle the disruption usually just
fine. It's the over 24 hour downtimes that get sketchy.
But one problem I'm having is that I use dyndns.com for my dns. I am
getting real tired of them, as they don't have colocation for their
servers, and their link seems real flaky lately. Along with the fact
that their boxes were down for about 8 hours last night and today
doesn't help out either.
I tried to get granitecanyon.com to work but never got the DNS record to
stick and get propagated. Have you had any problems with them? I like
the fact that they let you edit your DNS entry yourself, allowing you to
set up things like MX forwarders (dyndns doesn't even have a MX record
for my domain at all, so I can't offer to help you out...hmm, maybe I
should switch...)
greg k-h
[EMAIL PROTECTED]
On Fri, Jan 28, 2000 at 06:13:21PM -0800, [EMAIL PROTECTED] wrote:
>
> I've got a linux box that is hosting one of my domains
> that I formerly had at another ISP - nice to save the
> $30 monthly.
>
> It's also my mail server (qmail). I like it, but
> I'm worried about the reliability of my DSL connection
> and the times when I need to bring my machine down
> for short time periods.
>
> But if any of you are in the same situation we might
> be able to help each other out by being each other's
> backup MX forwarders? If my system goes down, incoming
> mail would queue up on your machine until mine came
> up again, and vice versa. I don't know much about
> the DNS stuff yet (I'm managing mine through
> granitecanyon.com) but wouldn't something like that
> make sense? Better redundancy all around, especially
> if were using different providers. Is this a good idea?
>
> Curt
