On Fri, Jul 25, 2003 at 02:53:20PM +0100, Philip Hazel wrote:
>
> If an item in a list of hosts for the manualroute router is of the
> form <domain>/MX then it represents the list of hosts defined by the
> MX records for that domain, in the order defined by the MX preference
> values. The use of this syntax implies "bydns" for this item, because
> MX records can be found only in the DNS.
Yep. That makes sense. I take it that:
ukc.ac.uk. 21h30m18s IN MX 5 pat.ukc.ac.uk.
ukc.ac.uk. 21h30m18s IN MX 5 greendale.ukc.ac.uk.
ukc.ac.uk. 21h30m18s IN MX 5 quicksilver.ukc.ac.uk.
ukc.ac.uk. 21h30m18s IN MX 7 mercury.ukc.ac.uk.
would map to:
pat.ukc.ac.uk:greendale.ukc.ac.uk:quicksilver.ukc.ac.uk:+:mercury.ukc.ac.uk
and not just:
pat.ukc.ac.uk:greendale.ukc.ac.uk:quicksilver.ukc.ac.uk:mercury.ukc.ac.uk
It's key that it load balances accross the equal priority hosts. If it maps
to the above then together with the randomize option will enable us to
emulate bydns completely AFAIUI.
> Come to think of it, a general feature "name/MX" meaning "the hosts to
> which this domain routes by MX" might have other applications.
Indeed.
> > A final option might be for us to patch the code ourselves to re-introduce
> > this option.
>
> Relax. I think I have just surrendered. :-)
Is the threat of my C coding that bad? :-)
> I'll take a look at the code and see what seems like a nice way to go on
> this one.
Thanks,
Darren
