Re: Changing servers
On Wednesday 21 March 2001, at 8 h 34, the keyboard of Steve [EMAIL PROTECTED] wrote: RedHat) to a debian server. I'm trying to figure out a way that will cause least mail delays to our customers whilst the dns records propagate (The IP's are going to change for the mail server). a) lower the TTLs to almost zero b) wait $OLDTTL + $REFRESH seconds c) change the infos d) after checking, put the TTLs back to the normal value That way, the change is instantaneous. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Changing servers
On Wed, Mar 21, 2001 at 08:34:56AM +, Steve wrote: Hi, I'm about to change a busy server (currently running under RedHat) to a debian server. I'm trying to figure out a way that will cause least mail delays to our customers whilst the dns records propagate (The IP's are going to change for the mail server). In addition to the allready mentioned changing of TTL's for the domain you can also do a regular portforward (of the sendmail port) from the old machine to the new machine untill DNS has updated. Also, I haven't come up with an easy solution for pop mail. Same solution... Mark Janssen Unix Consultant @ SyConOS IT E-mail: [EMAIL PROTECTED]GnuPG Key Id: 357D2178 http: markjanssen.homeip.net and markjanssen.[com|net|org|nl] Fax/VoiceMail: +31 20 8757555 Finger for GPG and GeekCode PGP signature
RE: Changing servers
RedHat) to a debian server. I'm trying to figure out a way that will cause least mail delays to our customers whilst the dns records propagate (The IP's are going to change for the mail server). a) lower the TTLs to almost zero b) wait $OLDTTL + $REFRESH seconds c) change the infos d) after checking, put the TTLs back to the normal value That way, the change is instantaneous. You could also, if you are planning to drop the old server offline immediately upon getting the new server running properly, set this up using MX records. Set the new server's IP as a lower priority MX in the DNS files and wait for it to propagate and then drop the old server offline. The SMTP hosts on the other end *should* then automatically switch to the lower priority MX record when they see that the normal MX host is unreachable and start sending to it. You can then at your leisure set your DNS files to the proper MX and let them propagate as normal with no interruption in service. Good luck! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Changing servers
On Wednesday 21 March 2001, at 8 h 34, the keyboard of Steve [EMAIL PROTECTED] wrote: RedHat) to a debian server. I'm trying to figure out a way that will cause least mail delays to our customers whilst the dns records propagate (The IP's are going to change for the mail server). a) lower the TTLs to almost zero b) wait $OLDTTL + $REFRESH seconds c) change the infos d) after checking, put the TTLs back to the normal value That way, the change is instantaneous.
Re: Changing servers
On Wed, Mar 21, 2001 at 08:34:56AM +, Steve wrote: Hi, I'm about to change a busy server (currently running under RedHat) to a debian server. I'm trying to figure out a way that will cause least mail delays to our customers whilst the dns records propagate (The IP's are going to change for the mail server). In addition to the allready mentioned changing of TTL's for the domain you can also do a regular portforward (of the sendmail port) from the old machine to the new machine untill DNS has updated. Also, I haven't come up with an easy solution for pop mail. Same solution... Mark Janssen Unix Consultant @ SyConOS IT E-mail: [EMAIL PROTECTED]GnuPG Key Id: 357D2178 http: markjanssen.homeip.net and markjanssen.[com|net|org|nl] Fax/VoiceMail: +31 20 8757555 Finger for GPG and GeekCode pgpayu9J4wgTG.pgp Description: PGP signature
Re: Changing servers
At 3/21/01 03:34 AM, Steve wrote: The current server runs sendmail and the replacement is running postfix. What I would like to do at the changeover is to get sendmail to automatically relay any incoming mail over to the new machine based on it's IP and let the new machine handle distribution. Is there an easy way to do this with sendmail? From sendmail.cf: # who gets all local email traffic ($R has precedence for unqualified names) DHhurricane.home.lan This causes any mail that comes into this box to be passed on to hurricane.home.lan for local delivery. I do this on my home network so that I only have one central mailserver. The gateway machines (as well as all the other UNIX/Linux machines) forward any incoming mail on to hurricane. HTH. -jg -- Jeremy L. Gaddis [EMAIL PROTECTED] Go away or I will replace you with a very small shell script.
RE: Changing servers
RedHat) to a debian server. I'm trying to figure out a way that will cause least mail delays to our customers whilst the dns records propagate (The IP's are going to change for the mail server). a) lower the TTLs to almost zero b) wait $OLDTTL + $REFRESH seconds c) change the infos d) after checking, put the TTLs back to the normal value That way, the change is instantaneous. You could also, if you are planning to drop the old server offline immediately upon getting the new server running properly, set this up using MX records. Set the new server's IP as a lower priority MX in the DNS files and wait for it to propagate and then drop the old server offline. The SMTP hosts on the other end *should* then automatically switch to the lower priority MX record when they see that the normal MX host is unreachable and start sending to it. You can then at your leisure set your DNS files to the proper MX and let them propagate as normal with no interruption in service. Good luck!
