[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Moving to new NOC
- Subject: Re: [cobalt-users] Moving to new NOC
- From: shimi <shimi@xxxxxxxxxxxxxxxx>
- Date: Fri May 18 12:40:35 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Tue, 8 May 2001, Rodolfo J. Paiz wrote:
> OK, everybody, I'm on countdown now. We move to our new digs (well, our
> first own digs) next Monday night. I've got my DNS timeout settings cranked
> down to 1 hour already, and will let them sit this way until Sunday when
> I'll change them to 1 minute.
>
> The new NOC is now live and behind a firewall. I can put servers into it
> without a problem, so I'm going to use my notebook as a server for 24 hours
> while I move the big one and verify that everything works well.
>
> Apache was not a problem.
> DNS is not a problem.
> The registries are, well, a problem but I'm working on them.
>
> However, what I have not figured out is how to avoid mail from being
> interrupted. From what I see, I have to do the following:
>
> * Install and configure sendmail on my notebook (mail2.domain.com) to
> receive mail for all my domains.
>
> * Create an A and an MX record with a higher cost to my notebook for each
> domain.
>
> So far, so cool. Now when the main server suddenly goes off-line, mail will
> be routed to mail2, the backup "server".
>
> But... how do I tell mail2 not to do local delivery, but rather to relay
> only and to queue only so that it collects mail, then waits until it can
> actually get to the better mailserver (smtp.domain.com) and sends it all
> the queued mail when smtp.domain.com resumes operations?
>
> I hope the question is clear; thanks, y'all.
unless ur downtime will be higher than 4 hours... nothing to worry about.
mailservers try to deliver for 4 hours and only if unsuccessful by then,
sends a warning message back, and STILL trying to deliver for 5 days.
This has not been tested though, so don't count on my words :)
>
>
> --
> Rodolfo J. Paiz
> rodolfo@xxxxxxxx
>
- shimi