On Mon, 25 Feb 2008, Henrik Nordström wrote:
mån 2008-02-25 klockan 17:30 +1100 skrev Tim Connors:
So it's already meant to be doing this (by caching bad status, I presume
you mean it doesn't keep trying that ip?)? Is that perhaps in the 3.x
branch? One host that has this wrong is an
dig +recurse +additional +authority +notrace A google.com.au
(which I freely admit I could be using wrong, or my upstream
ncsd server
on the host I am on now and exhibited these problems before,
could be silly)
I think it would be highly unlikely that google would be advertising a dead
On Mon, 25 Feb 2008, Henrik Nordström wrote:
sön 2008-02-24 klockan 03:54 +1100 skrev Tim Connors:
I am having trouble on two machines on two completely different networks,
both using squid -- for months now, a reasonably portion of the time,
squid fails to get through to google.com.au
mån 2008-02-25 klockan 17:30 +1100 skrev Tim Connors:
So it's already meant to be doing this (by caching bad status, I presume
you mean it doesn't keep trying that ip?)? Is that perhaps in the 3.x
branch? One host that has this wrong is an ancient distribution with
2.5.STABLE14 on it
sön 2008-02-24 klockan 03:54 +1100 skrev Tim Connors:
I am having trouble on two machines on two completely different networks,
both using squid -- for months now, a reasonably portion of the time,
squid fails to get through to google.com.au for the first minute. A
tcpdump revealed that
That sounds plausable. I'm surprised it isn't doing that already.
Throw it into a bugzilla report so it isn't forgotten.
Adrian
On Sun, Feb 24, 2008, Tim Connors wrote:
I am having trouble on two machines on two completely different networks,
both using squid -- for months now, a reasonably
