What do you mean when you hit your ip address? You mean the url? or the ip address? and are you trying to get there from the same lan or from the wan side? If you type
http://zimbra.localnet on any other machine than the zimbra server itself it's not going to resolve unless you have a dns server on your lan to resolv it for you and then you would have to have the dns server listed as such in either ifconfig(*nix) or ipconfig(windows). As far as vhosts go, I would suggest running another machine and let zimbra run alone.
Quote:
|
Originally Posted by tERRiON Hi there,
I'm playing around with Zimbra for several days now, and there's a small problem I'm facing:
I would like to use Zimbra behind a firewall with NAT. Until today I'm using more than one server on one public IP, using portforwarding.
This is my current setup:
port 21 forwards to 10.0.0.a (other machine)
port 25 forwards to 10.0.0.b (other machine; should be redirected to Zimbra when Zimbra is working like I would like to see it working)
port 80 forwards to 10.0.0.c (zimbra.localnet)
port 443 forwards to 10.0.0.c (zimbra.localnet)
(there are several more machines which aren't relevant)
The zimbra-box has hostname "zimbra.localnet" with a private IP-address. But when I hit my public IP address in my browser at work, I can't connect because zimbra.localnet can't be found.
A second question: Is there a possibility to config some Apache-like vhosts? I would like to host another website too. |