dpuryear
03-26-2003, 06:41 PM
First, I like DSM. It's nice software. Very nice interface. Good job guys. However, I do see one problem and I'm hoping someone here has a solution.
We have our web server behind a firewall. The firewall has the public IP and we assigned a private IP to our web server. All fine and dandy. This is how we have managed both a FreeBSD web farm and a farm built using a Linux Networx cluster. (One of the DSM guys told me that using a private IP on a webserver can cause problems. I have yet to see any problems with this kind of configuration to date until we hit this snag with DSM.)
Unfortunately, whenever we tried to add a domain with DSM it creates the zone with the local IP. I suspect it does some other odd things when using the private IP rather than allowing us to give it a public IP address to use when creating zones and so forth.
Is there a way for us to get around this issue with DSM?
If not we are just going to create an interface alias eth0:1 with the public IP and then tell DSM that is our IP address rather than the private IP.
We have our web server behind a firewall. The firewall has the public IP and we assigned a private IP to our web server. All fine and dandy. This is how we have managed both a FreeBSD web farm and a farm built using a Linux Networx cluster. (One of the DSM guys told me that using a private IP on a webserver can cause problems. I have yet to see any problems with this kind of configuration to date until we hit this snag with DSM.)
Unfortunately, whenever we tried to add a domain with DSM it creates the zone with the local IP. I suspect it does some other odd things when using the private IP rather than allowing us to give it a public IP address to use when creating zones and so forth.
Is there a way for us to get around this issue with DSM?
If not we are just going to create an interface alias eth0:1 with the public IP and then tell DSM that is our IP address rather than the private IP.