MX records and network cutovers.

Barry Margolin barmar at genuity.net
Tue Jan 29 15:02:27 UTC 2002


In article <Pine.GSO.4.21.0201281759030.3437-100000 at isis.visi.com>,
 <bofh at visi.com> wrote:
>The second option is along the same lines, with normal
>secondary/backup MX records, e.g.:
>
>		mail1		IN A 10.10.10.10
>		mail2		IN A 172.16.4.1
>		
>		podunk.com	IN MX 10 mail1
>				IN MX 20 mail2

This is usually the preferred solution.

>Both mail1 and mail2 are in the domain, and can talk with the
>internal mail server.  But will mail2 just queue mail, attempting 
>to deliver mail to mail1 due to its lower MX value? Or, will it
>send mail to the internal mailserver, and I can modify mail1 later?

It will do whatever you configure it to.  If it's configured to deliver
mail for pudunk.com locally, it will deliver it.  If not, it should look
for an MX record with lower preference level.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list