On 18/02/2004, at 12:21 am, George Macomber wrote:
This seems to work. Based on just one test. Am I asking for trouble in a way that I haven't foreseen? Is there a better solution?
If you have an internal DNS that's also behind the NAT (ie. not used to host your public DNS entries) I'd suggest adding an A rec and MX recs for the domains that point to the private IP address of the second server. If that's not an option you could just add said entries to a host file on the G3, ie.
The public DNS (and hence the rest of the world) sees:
A record -> Public IP of the NAT MX records for each domain pointing to the A rec above.
The G3 sees (either by use of a private DNS or hosts file on that machine):
A record -> Private IP of the Primary SIMS server MX records for each domain pointing to the A rec above.
I use this method on my work's network to protect an Exchange server (yeah, I know...) and the internet from each other, ie. the NAT forwards port 25 to the SIMS box (a rusty but trusty 8100/80av), SIMS then does spamtrapping, RBL lookups etc, then forwards the mail to the Exchange server. It's happily handling seven domains this way.
HTH, and cheers,
Paul.
############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
