Varnish on stand-alone server

[Stalker, Tim]

It would seem that if running varnish on its own server, the backend host must point to a fqdn.

________________________________
From: Stalker, Tim
Sent: Wednesday, January 18, 2017 11:28:45 PM
To: varnish-misc at varnish-cache.org
Subject: Varnish on stand-alone server


I'm setting up a web development cluster with 3 or 4 backend webservers. Because this is all offline at the moment, provisioning this with vagrant and ansible in a private network of servers with no fqdn. I have no problem getting varnish to connect to the backends over port 80 from within the varnish VM itself over lynx and curl, but from outside the VM on my host machine, varnish is unaware of the backends. Varnish works fine if I install it on the same machine as apache but if I try to run it in its own virtual machine. I would like to simulate a production environment as much as possible when all of the server names are fully qualified.


Can anyone suggest ways I might get varnish to provide caching from browsers on my host machine while running in its own virtual machine in a cluster?


Thanks a ton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20170119/75fb073b/attachment.html>