hi tony,
>> this -- seemingly -- prevents the delivery from 'mail.domain1.com' to
>> 'mail.domain2.com' using the dnslookup router.
>>
>> what's the cleanest way to deal with this?
>
> In general you should not put MX records in the (public) DNS which refer
> to RFC 3330 IP addresses. This kind of setup requires private email
> routing arrangements.
good point! but, i need to provide you with more info abt my setup
i do NOT broadcast my NATd-LAN RFC3330 addresses to the 'outisde' ...
rather, i've BIND9 as my DNS server, and use its 'views' capabilities.
machines OUTSIDE the lan querying the DNS see the assigned external addresses
of my router ports, which are then properly address & port mapped to my
internal boxes. in effect the private DNS you mention/suggest.
internal addresses see a configuration of RFC3330-space direct IP addresses of
all my variou boxes & services ... *including* the MX records.
i.e.,
dig @any.external.dns.server my.domain.com MX
A.B.C.D (<-- 'real' IP)
dig @my.dns.server my.domain.com MX, when outside my LAN
A.B.C.D (<-- 'real' IP)
dig @my..dns.server my.domain.com MX, when inside my LAN
10.0.0.6 (RFC3330 IP)
given this config, i still have my earlier question ... how best to have exim
handle it?
thx!
cheers,
richard
