RE: [squid-users] dns lookups

> -----Original Message-----
> From: D & E Radel [mailto:radel@inet.net.nz]
> Sent: Tuesday, May 10, 2005 9:06 PM
> To: Kevin; squid-users@squid-cache.org
> Subject: Re: [squid-users] dns lookups
>
>
> From: "Kevin" <kkadow@gmail.com>
>
>> If you reconfigure squid using the "--disable-internal-dns" flag,
>> recompile, and re-install, squid will go back to the old behavior of
>> using "dnsserver" with the system resolver library (which obeys
>> /etc/resolv.conf), instead of the embedded DNS code.
>>
>> This should address your problem, but may cause other
>> problems in the long run. The "--disable-internal-dns" configure
>> option is deprecated, as the dnsserver solution is inefficient,
>> does not scale well. This could work out okay on a lightly loaded
>> cache serving a limited number of users.
>
> Thanks for that info Kevin. I use the binary packages from Debian because
> 'They Just WorkT'. Compiling my own packages are not an option for me at
> present. A Proxy Automatic Configuration script might be the best long
term
> solution. I would've thought that there would be "disable_internal_dns"
> option or something to that extent in the squid.conf. I mean if a PAC
script
> can do it without a recompile..... Thanks again Kevin.
>
> regards,
> Dietrich

If you are able to ping a domain-name-less box from the command line, but
can't surf to it through Squid, then you should check your squid.conf for
the dns_nameservers directive (make sure it's commented). Squid, by default
will use the /etc/resolv.conf file to determine which DNS servers to query,
and is capable of proxying single entry hosts.

Chris
Received on Wed May 11 2005 - 11:08:26 MDT