Yes I have tried to connect by name. I have an acer revo running as a client machine which has XBMC on it. The XMBC has a web gui enabled on port 80. If I set proxy_pass
http://revo.home.lan.... it takes me right to the XBMC web interface.
So I know NGINX works, but unfortunately not for my vhost. This might not be a complete problem since all I have to do is just not use vhost for either the external website of zarafa mail service. I just liked the vhost approach because you can force SSL .... with zarafa this made it easier than having to reconfigure the zarafa files themselves to automatically go to HTTPS version.
With hardware not being an issue... what do you think about making a virtual server as zentyal slave... installing a full lamp stack and zarafa (basically using it for just webserver and mail). This way I can get NGINX to point right at it by name and possibly avoid the vhost problem?
?