Re: [squid-users] using parent cache and parent dns

On Tue, 09 Feb 2010 16:42:18 -0900, Chris Robertson <crobertson_at_gci.net>
wrote:
> im notreal wrote:
>> Basically here is my setup:
>>
>> I have a cache located on an oil rig
>> down south and one in the home office. There is a dns in the home
>> office that I don't have access to on the rig, and there is one on the
>> rig. There are webservers in both locations (management and control
>> stuff) that I need access to. What I'd like to do is be able to
>> forward requests to the parent without having to resolve them locally.
>>
>> if
>> i do a dns_nameserver 127.0.0.1 I won't be able to split the requests
>> between both sites (i.e. !somewebserver.local won't be resolved locally
>> and will fail)
>>
>> ideas ?
>>
>
> Use never_direct (http://www.squid-cache.org/Doc/config/never_direct/)
> in association with a dstdomain ACL. Any matching domains should not
> attempt resolution, but will send the request to the appropriate peer
> (as defined by your cache_peer_access rules).

Um, this is a fairly basic reverse-proxy requirement.

"im notreal" take a look through
http://wiki.squid-cache.org/ConfigExamples#Reverse_Proxy_.28Acceleration.29
under reverse proxy. You can decide whether the peer configured is the
other proxy, or the web server at the other site. Depending on your network
layout and security one or other will work.

All you have to be careful of is that the ACLs used in cache_peer_access
and http_access use dstdomain instead of dst or anything else based on DNS.

Amos
Received on Wed Feb 10 2010 - 02:04:23 MST