RE: [squid-users] SSL-bump DNS lookup issue

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Tue, 11 Feb 2014 11:15:29 +1300

On 2014-02-11 10:57, Darren Breeze wrote:
> Hi and Thanks Amos
>
> scanning the log there is a successful DNS lookup but is seems to fail
> looking up a key once it gets a valid IP address
>
<snip>

> 2014/02/08 23:27:55.261| peer_select.cc(286) peerSelectDnsPaths: Found
> sources for 'ssl.gstatic.com:443'
> 2014/02/08 23:27:55.261| peer_select.cc(287) peerSelectDnsPaths:
> always_direct = ALLOWED
> 2014/02/08 23:27:55.261| peer_select.cc(288) peerSelectDnsPaths:
> never_direct = DENIED
> 2014/02/08 23:27:55.261| peer_select.cc(292) peerSelectDnsPaths:
> DIRECT = local=[::] remote=[2404:6800:4005:c00::78]:443 flags=1
> 2014/02/08 23:27:55.261| peer_select.cc(292) peerSelectDnsPaths:
> DIRECT = local=0.0.0.0 remote=74.125.128.120:443 flags=1

Okay, DNS is working fine.

It found the two possible destinations for this request. The IPs:
  2404:6800:4005:c00::78
  74.125.128.120

I assume this is what you mean by "failure"? :

> 2014/02/08 23:27:55.261| pconn.cc(436) pop: lookup for key
> {[2404:6800:4005:c00::78]:443/ssl.gstatic.com} failed.

... that is attempting to find an existing open connection to the server
on that IP:port. It is normal not to have one on first connecting to a
site.

Any pconn pop() failure should be followed by an attempt to open a new
TCP connection to that IP:port.

Amos
Received on Mon Feb 10 2014 - 22:15:38 MST

This archive was generated by hypermail 2.2.0 : Tue Feb 11 2014 - 12:00:08 MST