Thanks for the reply No good though I'm afraid, as we'd have to local host the entire internet - the failed DNS lookups are for the other 9,999 clients trying to look up whatever web site they're trying to access, I.E.: 2005/03/21 10:48:57| WARNING: All dnsserver processes are busy. 2005/03/21 10:48:57| Consider increasing the number of dnsserver processes in your config file. 2005/03/21 10:48:58| dnsSubmit: queue overload, rejecting landingstrip.dell.com 2005/03/21 10:48:58| dnsSubmit: queue overload, rejecting games-att.espn.go.com 2005/03/21 10:48:58| dnsSubmit: queue overload, rejecting baym-wm2.webmessenger.msn.com 2005/03/21 10:48:58| dnsSubmit: queue overload, rejecting walgreens.com 2005/03/21 10:48:58| dnsSubmit: queue overload, rejecting pgq.yahoo.com Also of note, we have dnsserver processes configured to the maximum of 32 per server. Thanks again for the reply Fred --- Kinkie <kinkie-squid@xxxxxxxxx> wrote: > On Tue, 2005-03-22 at 10:37 -0800, Fred Clark wrote: > > Hello all > > > > I'm having a very strange issue with our squid > cluster > > and our Plumtree Portal. > > > > This is more of a workaround than a fix, but if the > number of important > sites is not big, why not using /etc/hosts? This way > the DNS lookup > process would be synchronous for squid in any case. > > Kinkie > __________________________________ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250
