John Rudd wrote:
[snip]
Why not have:
- domain.tld have an A record (IP addr A)
- web server listens to IP addr A on a virtual network interface. (in
addition to listening to its regular IP addr on whatever other network
interface it already has)
- the only ports listening on IP addr A
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
Jeff Rife wrote:
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:
On 14 May 2006 at 13:10, Ben Kamen wrote:
Not really. I have multiple machines with multiple services being a single
public IP. The trick is to
make sure the ports are different. I use a Netscreen 5XP and it handles this
method (port based mapping)
as well as a full IP to IP mapping just
On May 14, 2006, at 5:53 AM, netguy wrote:
John Rudd wrote:
[snip]
Why not have:
- domain.tld have an A record (IP addr A)
- web server listens to IP addr A on a virtual network interface. (in
addition to listening to its regular IP addr on whatever other
network interface it already
5 matches
Mail list logo
