ok, here's the deal. this is at work, so the obvious solution is not even
possible, since the answer is no.
we have a private network here at work. it is connected to a machine in an
exodus cage by a T1 and the machine in the cage has an internet connection
on the other side. no routing is done. there is no way to get directly
from the internal network to the internet. the only way to get to the internet
is through a proxy server. we are currently using an ancient copy of netscape
proxy server. nps blows. it crashes constantly, and we want to get away from
it. in addition, it has been mandated by corporate that all sub-companies
will be using squid as their proxy server by the end of the year.
so i need to setup two servers. one on the exodus box, and one internally.
no-one has direct access to the exodus box, so they have to go through the
internal proxy server to get bounced through the external proxy server to get
internet content.
i've set this up, and not being able to set them up as peers, a friend said
i should look at setting the internal one up as an httpd-accelerator and
pointing it at the external one. the only problem with this, however, is
that the internal copy of squid is trying to do its own dns resolution, which
is never going to work since the machines on the internal network cannot
resolve internet addresses. the way the nps boxes do it is the internal
proxy asks the external proxy for dns info.
how do i get the internal squid server to ask the external squid server for
dns resolution instead of trying to do it itself?
-brian
-- "You know, evil comes in many forms, be it a man-eating cow or Joseph Stalin. But you can't let the package hide the pudding. Evil is just plain bad! You don't cotton to it! You gotta smack it on the nose with the rolled up newspaper of goodness! Bad dog! Bad dog!" -- The TickReceived on Thu Jun 05 2003 - 10:33:48 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:17:16 MST