RE: [squid-users] Resolving internal hosts

Also make sure that you set up Squid to spawn enough 'dnsserver' processes
to handle the lookups, keeping in mind that Squid caches lookups in the IP
cache (which, by the way, you never want to disable). In my case, I only
spawn 5 dnsserver instances because I have my Squid set up as an
accelerator, which only accesses a few boxes, which means thanks to IP
lookup caching in Squid, they are only used a few times at Squid startup
(well, only when the cache is cleared and Squid is restarted). If you run a
normal proxy, you would want more 'dnsserver' processes spawned...

Sean

-----Original Message-----
From: Pablo Sanchez [mailto:pablo@purecarbon.com]
Sent: Tuesday, September 25, 2001 1:46 PM
To: Graziano Sommariva; squid-users@squid-cache.org
Subject: RE: [squid-users] Resolving internal hosts

-----Original Message-----
From: Graziano Sommariva [mailto:graziano.sommariva@elsag.it]
Sent: Tuesday, September 25, 2001 2:11 PM
To: squid-users@squid-cache.org
Subject: [squid-users] Resolving internal hosts

Hello,

I'm testing squid 2.4STABL2 over a linux system 7.0.

It works fine ,but it does not resove internal hosts defined in /etc/hosts
file even I have the record "hosts: files dns" in /etc/nsswitch.

Why?
I had this very problem and Henrik provided me the solution. :)

This is working in the 2.5 release. For the 2.4 release, compile SQUID with

      --disable-inernal-dns
Once you do this, you'll be set. Works for me.
Later!

---
Pablo Sanchez         mailto:pablo@purecarbon.com
Ph  : 303.939.8897       Fax: 603.720.7723
Cell: 303.717.5889