[squid-users] DNS lookup fails initially for FQDN in squid

Antony Stone Antony.Stone at squid.open.source.it
Fri May 27 16:49:02 UTC 2016

On Friday 27 May 2016 at 17:51:36, Aashima Madaan wrote:

> > So, does the problem exist if you:
> > 
> > 1. Stop Squid
> > 2. Type "host short.domain.name" to resolve the ICAP server manually
> > 3. Start Squid
> > 
> > (The last two commands in as quick succession as possible - preferably on
> > a single line separated by a semi-colon)
> yes the problem still exists

That tells me that the problem is not DNS, then.

Command 2 verifies that DNS resolution is working.

Command 3 results in the problem.

Therefore whatever is causing the problem is not DNS.

> on additional debugging by switching on tcpflow, I see squid sends
> OPTIONS request to icap server and that is when it is able to resolve
> DNS and which brings the service up in 3 minutes.

Have you tried running some sort of packet tracer (eg: wireshark) to check 
when Squid is sending the DNS request, where it is sending it to, and whether 
it gets a response?

>  Address.cc(389) lookupHostIP: Given Non-IP 'short.domain.name': Name
> or service not known

Can anyone else shed some light on what this particular message means?


Wanted: telepath.   You know where to apply.

                                                   Please reply to the list;
                                                         please *don't* CC me.

More information about the squid-users mailing list