> If you run a local copy of bind (or your favourite DNS server) on the mail > server box (caching only - I suppose you could run an authoratative server
> on the mail box, but with bind's hate of anyone else using system memory
> this may not be a good plan :-) ), then you can get the A records
> randomised for any name.
Note that you may also want *REMOTE* systems to load balance ....
> However I guess that if you have a set of MX records with equal preference
> then they should be used in a random order, and the DNS doesn't do this
> for you.
It does, if using a RoundRobin NS.
However, that is under control of the manager of the NS at the *CLIENT* site,
rather than of the MTA *SERVER* manager ...
> So even if we decide that the A record issue can be punted to bind, the MX
> record issue cannot, in which case we might as well implement both...
