MX recond question

[Nate Duehr]

You could put in a second MX record for the new machine now and mail
will be delivered to the new machine as a "secondary" as soon as you
take the other one off-line forever.  Then you could update your zone to
remove the old record ...

Of course, if the new server isn't ready to go yet, then this is a
not-so-good idea.

In that case (or if you're really moving the existing server to a new
address), just lower the TTL ahead of time to something reasonable and
then make your changes, just like if you were moving any other server.

The chance of you losing any mail is slight, as most MTA's will retry at
least for a couple of days unless the admin has shortened the defaults.
At worst your mail would get delayed, not lost.

On Thu, Aug 31, 2000 at 10:11:19AM +0800, briz wrote:
> hi,
> we are migrating our mail server (mail.whatever.com) to a different machine.
> from 123.123.123.123 to 345.345.345.345
> currently we have
> 
> whatever.com. IN MX 10 mail.whatever.com.
> mail            IN      A       123.123.123.123
> 
> what are the better ways to do this, to minimize / eliminate the chances of
> lost mail? will setting up a secondary MX helps?
> 
> thanks!
> mok swee loong
> 
> 
> 
> 

-- 
Nate Duehr <nate at natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.

-- Attached file included as plaintext by Listar --

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE5rcgMLWF3xX7OwdIRAoySAJ96MrnXJOKUX9aXMpERWr5T5gl2gQCggQ7w
KLZBOeKrHnBhFrExYRuM350=
=xtGC
-----END PGP SIGNATURE-----