From: MERC::"uunet!WKUVX1.BITNET!list-mgr" 6-JUL-1992 10:29:33.31 To: MX-List@WKUVX1.BITNET CC: hornlo@okra.millsaps.edu Subj: Re: MX and VAXclusters Thanks for the suggestions on getting a cluster alias to work with MX. It turns out that adding the proper MX records on our nameserver helps a lot . It didn't work before because I didn't increment the "serial number" for the database. The following (edited) configuration makes a vanilla MX V3.1 installation work with either of these: user@okra.millsaps.edu user@millsaps.edu without having to separately define any logicals or rewrite rules. ----------- @ IN SOA uw1301.millsaps.edu. postmaster.uw1301.millsaps.edu. ( 9207043 ; Serial 300 ; Refresh - 5 minutes 60 ; Retry - 1 minute 1209600 ; Expire - 2 weeks 43200 ) ; Minimum - 12 hours IN NS uw1301.millsaps.edu. IN NS noc.sura.net. >> IN MX 10 okra01.millsaps.edu. >> IN MX 20 okra02.millsaps.edu. >> IN MX 30 mirage.millsaps.edu. ; ; Ultrix workstation uw1301 IN A 151.160.8.12 >> IN MX 0 uw1301.millsaps.edu. ; VAXcluster alias okra IN A 151.160.8.99 >> IN MX 10 okra01.millsaps.edu. >> IN MX 20 okra02.millsaps.edu. >> IN MX 30 mirage.millsaps.edu. ; ; VAXcluster nodes okra01 IN A 151.160.8.8 >> IN MX 0 okra01.millsaps.edu. okra02 IN A 151.160.8.11 >> IN MX 0 okra02.millsaps.edu. mirage IN A 151.160.8.3 >> IN MX 0 mirage.millsaps.edu.