Hi,
I would suggest that you try the following as well:
in your /etc/resolv.conf add 127.0.0.1 as a name server if squid and the
DNS server is running on the same machine. The reason for this is to give
the resolver time to get the request.
The "better" way would be to give DNS traffic a higher priority on the
link.
Cheers,
Pieter
On Mon, 11 Aug 2008, Mr Crack wrote:
I setup caching only name server and squid also use my local caching
only name server on the same machine
--- /etc/resolv.conf -----------
nameserver 192.168.77.254
--------------------------------------
Here is cache.log output
2008/08/11 09:54:00| DNS Socket created at 0.0.0.0, port 32857, FD 8
2008/08/11 09:54:00| Adding nameserver 192.168.77.254 from /etc/resolv.conf
2008/08/11 09:54:00| Accepting proxy HTTP connections at 0.0.0.0, port
8080, FD 9.
2008/08/11 09:54:00| Accepting ICP messages at 0.0.0.0, port 3130, FD 11.
2008/08/11 09:54:00| WCCP Disabled.
2008/08/11 09:54:00| Configuring Parent 192.168.77.10/8080/0
2008/08/11 09:54:00| Loaded Icons.
2008/08/11 09:54:00| Ready to serve requests.
2008/08/11 09:54:02| temporary disabling (Bad Gateway) digest from 192.168.77.10
2008/08/11 09:59:02| temporary disabling (Bad Gateway) digest from 192.168.77.10
2008/08/11 10:09:02| temporary disabling (Bad Gateway) digest from 192.168.77.10
I will copy brower error... when my connection slow agin..
I thinks DNS timeout
On Mon, Aug 11, 2008 at 2:09 PM, Pieter De Wit <pieter@xxxxxxxxxxxxx> wrote:
Hi,
What error are you getting in the browser. I would suspect that your DNS is
timing out, perhaps look at that ?
Cheers,
Pieter
On Mon, 11 Aug 2008, Mr Crack wrote:
Dear All,
When connection is OK, squid is also OK.
But when connection is very slow... e.g. 2--5 Kbps, squid cannot show
visited sited from its cache...
Mr. Crack...007
