Henrik Nordstrom wrote: > mån 2006-08-21 klockan 06:40 +0000 skrev Monty Ree: > >> Is there any problem to set this? > > Exacly how it's meant to be done, except that perhaps you want to use > the real server IP addresses in squid.conf rather than DNS. Henrik, I too want to set up something with exactly this configuration. Whereabouts do the IPs go? Here's a stab at the configuration: http_port 192.168.26.26:80 vhost cache_peer 192.168.0.41 parent 80 0 no-query originserver name=cache cache_peer_domain server1 cache.example.com cache_peer 192.168.0.42 parent 80 0 no-query originserver name=images cache_peer_domain server1 images.example.com One other thing I'm not sure about is DNS resolution. I currently have this configuration: client -> LB1 -> squid farm -> LB2 -> apache farm LB1 & LB2 are load-balancers So, clients access cache.example.com which externally (i.e. public IP address) resolves to LB1. LB1 passes the request to a machine in the squid farm (squid01,02,03) The squid instances peer with each other and are configured as accelerators for the apache farm via LB2 proxy.example.com resolves to LB2 (192.168.0.41) LB2 passes the request on to a machine in the apache farm (proxy01,02,03) which are configured with cache.example.com as ServerAliases in httpd.conf. On each of the squid machines, I'm currently using this config (IP address different per machine): http_port 192.168.26.26:80 vhost cache_peer 192.168.0.41 parent 80 0 no-query originserver LB2 has address 192.168.0.41 However, I find that this only works if cache.example.com resolves internally to 192.168.0.41. Is this how it's supposed to work, or am I missing something? Basically, what I'd like to happen is : * all incoming requests for cache.example.com get passed to 192.168.0.41 * all incoming requests for images.example.com get passed to 192.168.0.42 This should happen regardless of what cache.example.com and images.example.com resolve to internally. Thanks, R.
