> > The dns resolution also must happen on the proxy > > side. > > Its extremely strange that the address resolution is > happening at the proxy side. If that's the case how is > your PC able to resolve the proxy's address? I don't > think that the address resolution is happening at the > proxy side. Can you please check and verify again? Its not that strange in corporate world to have external addresses resolve through proxy. Basically there _is_ a dns service active on intranet, and that is what finds the address for proxy. The issus is _not_ finding the internal sites. The external link however is the problem.Everything including dns is blocked and only way to fetch pages from outside is through proxy. Here is how the proxy mechanism ususally works. A client sends a request to proxy to fetch a particular web page. The _proxy_ fetches the web page using url provided by client. So whenever proxy is given a direct www.xyz.com address to fetch the dns resolution happens _at_proxy_side_. Now most browsers know this and when using proxy won't try to resolve the address by themselves. Unfortunately wget and others like ftp don't seem to have knowledge about this. So when i ask wget to fetch an address it tries to resolve the domain name first without even consulting proxy _even_if_ http_proxy variable is set. Which basically goes to intranet dns resovling mechanism and returns failure.There is a way in http_proxy protocol to ask the proxy to resolve a dns address. But there is no way in linux to reroute th system dns request to http_proxy :-(. > Simplest and the best is to enter an entry for the > proxy address in /etc/hosts. thats a non issue as i have proxy ip itself, and the dns can resolve internal adddresses.
BAIN -- ______________________________________________________________________ Pune GNU/Linux Users Group Mailing List: ([email protected]) List Information: http://plug.org.in/mailing-list/listinfo/plug-mail Send 'help' to [EMAIL PROTECTED] for mailing instructions.
