If RoundRobin is best practise/preferred solution, should I then do:
; zone file fragment
IN MX 10 mail.example.com.
....
mail IN A 192.168.0.4
IN A 192.168.0.5
IN A 192.168.0.6
or
; zone file fragment
IN MX 10 mail.example.com.
IN MX 10 mail1.example.com.
IN MX 10 mail2.example.com.
....
mail IN A 192.168.0.4
mail1 IN A 192.168.0.5
mail2 IN A 192.168.0.6
I think I would prefer the first solution - as a single hostname can be
distributed to "endusers".
Will this automatically interfere with our corporate mail on the same
domain - is there anything DHCP/DNS MX-to-clients update-wise I should be
aware of ?
Thanks in advance :) !
~maymann
2012/3/10 Michael Maymann <mich...@maymann.org>
> Hi List,
>
> I would like to setup a LoadShared Failover internal mail-relay solution
> (only for sending mail internal->external).
>
> My thoughts:
> - Setup virtual+physical server in same VLAN (different physical
> locations) with same OS+Postfix+config
> - Configure DNS RoundRobin
> - Have logging from both servers pointing to same NFS-dir and have awstats
> create statistics from there
> Internal traffic:
> - Requests would all be received on RoundRobin_IP, and therefore
> LoadShared between the servers
> - Answers would all be send through Server_IP
> External traffic:
> - All traffic is done through Server_IP
>
> 1. Are the clients ok with answers coming from different IP than send-to
> ... or how do I prevent this from disrupting client<->server communication
> - some PostFix/other magic ?)
>
> 2. What happens if one of my servers dies. Will RoundRobin still try to
> send traffic to it, and if so how will clients react on this ?
>
> 3. Would Bonding be a better solution for my purpose ?
>
> 4. Is there already a RHEL6 howto somewhere, that you can recommend ?
>
> 5. What is best practice ?
>
>
> Thanks in advance :-) !
> ~maymann
>
