On 31/07/2015 10:39 a.m., Mike wrote:
> I suspect this may be a bug with squid 3.4.x since this issue happened
> on 2 different squid servers, one is 3.4.6, another is 3.4.7. Yet on the
> backups to each, one has 3.5.1 and other has 3.5.6 (I updated it today),
> and they are not affected by this, b
On 7/30/2015 16:30 PM, Amos Jeffries wrote:
On 31/07/2015 3:48 a.m., Mike wrote:
On 7/27/2015 17:25 PM, Amos Jeffries wrote:
On 28/07/2015 8:38 a.m., Mike wrote:
Running into an issue, using the squid.conf entry
dns_nameservers 72.x.x.x 72.x.y.y
These are different servers (under our control)
On 31/07/2015 3:48 a.m., Mike wrote:
> On 7/27/2015 17:25 PM, Amos Jeffries wrote:
>> On 28/07/2015 8:38 a.m., Mike wrote:
>>> Running into an issue, using the squid.conf entry
>>> dns_nameservers 72.x.x.x 72.x.y.y
>>>
>>> These are different servers (under our control) for the purpose of
>>> filte
On 7/27/2015 17:25 PM, Amos Jeffries wrote:
On 28/07/2015 8:38 a.m., Mike wrote:
Running into an issue, using the squid.conf entry
dns_nameservers 72.x.x.x 72.x.y.y
These are different servers (under our control) for the purpose of
filtering than listed in resolv.conf (which are out of our cont
On 28/07/2015 8:38 a.m., Mike wrote:
> Running into an issue, using the squid.conf entry
> dns_nameservers 72.x.x.x 72.x.y.y
>
> These are different servers (under our control) for the purpose of
> filtering than listed in resolv.conf (which are out of our control, used
> for server IP routing by
Running into an issue, using the squid.conf entry
dns_nameservers 72.x.x.x 72.x.y.y
These are different servers (under our control) for the purpose of
filtering than listed in resolv.conf (which are out of our control, used
for server IP routing by upstream host).
The problem we found like th
