[squid-users] DNS lookup fails initially for FQDN in squid
Antony Stone
Antony.Stone at squid.open.source.it
Fri May 27 15:28:21 UTC 2016
On Friday 27 May 2016 at 17:10:48, Aashima Madaan wrote:
> > Please define "initially" - do you mean:
> >
> > - when the squid server is booted up
> > - when the squid service is started on an already-running server
> > - something else?
> >
> initially here means when I start squid service
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)
> I see in cache.log that its adding nameservers from /etc/resolv.conf
>
> 2016/05/27 10:32:52 kid1| Adding nameserver 10.32.1.1 from /etc/resolv.conf
> 2016/05/27 10:32:52 kid1| Adding nameserver 10.32.1.1 from /etc/resolv.conf
> 2016/05/27 10:32:52 kid1| Adding nameserver 8.8.8.8 from /etc/resolv.conf
Why have you added 10.32.1.1 twice?
> > Is that DNS server running and answering queries before the Squid
> > server/service starts up?
>
> I do curl/ping/nslookup for icap server from squid machine, it is able to
> resolve that particular ip.
You do this before starting Squid, and it works, and then when you start
Squid, it fails for 3 minutes??
Antony.
--
I wasn't sure about having a beard at first, but then it grew on me.
Please reply to the list;
please *don't* CC me.
More information about the squid-users
mailing list