On 14 May 2006 at 6:53, netguy wrote:
> I am a small provider ( tiny ) and have multiple hosted domains behind a
> firewall with smtp,pop3, imap and www all pointing to a server behind
> the firewall. I can't seperate out the ports. Having another machine
> just for www doesn't make any sense to me as my current machine does not
> use much CPU power as it is and it would just add to the overhead.
You don't need another machine...just have more than one IP address on
the server behind the firewall.
For example:
172.16.0.1: "base" IP
172.16.0.2: listens on port 80 only
172.16.0.3: listens on port 25 only
You (of course) need more than one public IP to pull this off:
192.0.2.1: forward to 172.16.0.1
192.0.2.2: forward to 172.16.0.2
192.0.2.3: forward to 172.16.0.3
Then, in DNS for domain.tld:
@ A 172.16.0.2
www A 172.16.0.2
@ MX 10 172.16.0.3
--
Jeff Rife |
|
http://www.nabs.net/Cartoons/RhymesWithOrange/WorkingDogs.gif
_______________________________________________
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list [email protected]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
