Well it could be something like the following, this kind of configuration is actually used:
MX 10 mx1.isp.com MX 10 mx2.isp.com A mx1.isp.com 123.123.123.1 A mx2.isp.com 123.123.123.2 A mx1.isp.com 123.123.123.2 A mx2.isp.com 123.123.123.1 I don't like it and can't say for sure it is flawless or not, it just causes confusion to my eyes :) --------------- Franco Celli [EMAIL PROTECTED] ----- Original Message ----- From: "Markus Gufler" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, December 24, 2004 10:48 AM Subject: RE: [Declude.JunkMail] OT: MX priorities > So to be sure the DNS zone file should contain > > MX 10 mx1.isp.com > MX 10 mx2.isp.com > MX 20 mx1.isp.com > MX 20 mx2.isp.com > > Or > > MX 10 mx1.isp.com > MX 10 mx2.isp.com > MX 20 mx1_bkp.isp.com > MX 20 mx2_bkp.isp.com > > also if the "bkp" entries resolve to the same IP's? > > Markus > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Franco Celli > > Sent: Friday, December 24, 2004 10:27 AM > > To: [email protected] > > Subject: Re: [Declude.JunkMail] OT: MX priorities > > > > Hi Markus, > > I cannot say I'm an expert but as far as I know "it should". > > > > The configuration you described is not a DNS round robin, > > where you tipically assign two or more IPs to same hostname. > > In this case the client DNS cache will cause the remote MTA > > to connect to a single IP until it expires (In windows you > > should reboot the machine). > > > > In you example you defined two different MX records with same > > priority I don't know wich one will be picked up first, it is > > also possible you will never achive a 50% load, but if anyone > > fails I believe a well programmed DNS/MTA SHOULD connect to the other. > > > > > > --------------- > > Franco Celli > > > > > > > > ----- Original Message ----- > > From: "Markus Gufler" <[EMAIL PROTECTED]> > > To: <[email protected]> > > Sent: Friday, December 24, 2004 10:11 AM > > Subject: [Declude.JunkMail] OT: MX priorities > > > > > > > I've a question I can't answer by just testing it out on my > > MTA because I > > > don't know if other MTA's will do the same thing. > > > > > > If I have 2 front end gateways servers > > > > > > IP1: 123.123.123.1 > > > IP2: 123.123.123.2 > > > > > > A mx1.isp.com 123.123.123.1 > > > A mx2.isp.com 123.123.123.2 > > > > > > And set up MX-records for domain.com like > > > > > > MX 10 mx1.isp.com > > > MX 10 mx2.isp.com > > > > > > The DNS ist configured to answer in round robin method. > > > So the load should be 50/50 on both servers. > > > > > > Now the question: should or must a remote MTA try to > > connect to the second > > > MX 10 host if the first one (also with priority 10) was not > > reachable? > > > > > > Is this a "must have" or could it be that some MTA's from > > certain vendors > > > will not connect to the second MX? > > > > > > Thanks in advance > > > Markus > > > > > > > --- > > [Quipo ISP - Questa E-mail e' stata controllata dal programma > > Declude Virus] > > [Quipo ISP - This E-mail was scanned for viruses by Declude Virus] > > > > --- > > [This E-mail was scanned for viruses by Declude Virus > > (http://www.declude.com)] > > > > --- > > This E-mail came from the Declude.JunkMail mailing list. To > > unsubscribe, just send an E-mail to [EMAIL PROTECTED], and > > type "unsubscribe Declude.JunkMail". The archives can be found > > at http://www.mail-archive.com. > > > > > > > --- > [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] > > --- > This E-mail came from the Declude.JunkMail mailing list. To > unsubscribe, just send an E-mail to [EMAIL PROTECTED], and > type "unsubscribe Declude.JunkMail". The archives can be found > at http://www.mail-archive.com. > --- > [Quipo ISP - Questa E-mail e' stata controllata dal programma Declude Virus] > [Quipo ISP - This E-mail was scanned for viruses by Declude Virus] > > --- [Quipo ISP - Questa E-mail e' stata controllata dal programma Declude Virus] [Quipo ISP - This E-mail was scanned for viruses by Declude Virus] --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
