The other solution, which is what I usually have done is to setup an authoritative DNS server for your
domain that only serves out DNS for your LAN. Then point
acc3ss.homelinux.org to whatever your internal IP Addresses are and setup
MX records for it too if you want. That way anyone outside of your
network resolves to your firewalls external address but anyone on your
internal network would resolve to your firewall/mailservers internal
address. Hope this helps.
This is the method I would use. It tends to work the best and you aren't involving your nat box when you don't need to which will give you better performance. Though I am not sure the performance hit caused by passing the internal traffic through the firewall will be noticeable. I expect it won't be.
regards, -- Mark Lane, CET mailto:[EMAIL PROTECTED] Hard Data Ltd. http://www.harddata.com T: 01-780-456-9771 F: 01-780-456-9772 11060 - 166 Avenue Edmonton, AB, Canada, T5X 1Y3 --> Ask me about our Excellent 1U Systems! <--
BEGIN:VCARD VERSION:2.1 N:Lane;Mark FN:Mark Lane ORG:Hard Data Ltd. TITLE:Sales TEL;WORK;BUSINESS:780-456-9771 TEL;WORK;VOICE:780-456-9771 TEL;WORK;FAX:780-456-9772 ADR;WORK:;;11060 - 166 Avenue;Edmonton;AB;T5X1Y3;Canada LABEL;WORK;ENCODING=QUOTED-PRINTABLE:11060-166 Avenue=0D=0AEdmonton, AB T5X1Y3=0D=0ACanada URL;WORK:http://www.harddata.com EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20010222T231737Z END:VCARD
