Bug#604775: squid3: Can't access www.google.com when using bind as DNS server

Thanks Joerg, so this bug was caused by your non-default setting of dns_v4_fallback to off, right? Regards, L Il giorno 22/feb/2011, alle ore 10.48, Joerg Schuetter ha scritto: Upgrading to 3.1.11 had the same result. Setting dns_v4_fallback to on (default) as suggested by Amos solved the

Bug#604775: squid3: Can't access www.google.com when using bind as DNS server

Hello Luigi That's exactly the case. Sorry for that. Joerg -Original Message- From: Luigi Gangitano [mailto:lu...@debian.org] Sent: Wednesday, March 02, 2011 5:13 PM To: Schuetter, Joerg Cc: 604...@bugs.debian.org Subject: Re: Bug#604775: squid3: Can't access www.google.com when using

Bug#604775: squid3: Can't access www.google.com when using bind as DNS server

Upgrading to 3.1.11 had the same result. Setting dns_v4_fallback to on (default) as suggested by Amos solved the issue. Thanks Joerg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#604775: squid3: Can't access www.google.com when using bind as DNS server

Hi Joerg, I fail to see how this is a squid3 bug. From your wireshark dumps, the three DNS queries have three different answers and squid fails to work with the one that does not contain full response (either an + CNAME or an A record). Suid3 fails to work when the server gives broken

Bug#604775: squid3: Can't access www.google.com when using, bind as DNS server

I believe this is related to the use of dns_v4_fallback off. That option prevents Squid performing a DNS A lookup if there is any kind of positive response from an lookup. In the case of www.google.com there is always a positive CNAME result. lookup produces a positive CNAME-only

Bug#604775: squid3: Can't access www.google.com when using bind as DNS server

Hi Joerg, Sorry for the late answer. :-( I cannot actually reproduce this bug and see any difference in the host resolution example you posted. I also fail to see any relevant difference in the host output you attached to the bug report, apart from the response size being different (104 bytes

Bug#604775: squid3: Can't access www.google.com when using bind as DNS server

Hello Luigi There is no error.log, the request simply times out. I have 3 wireshark-dumps (text only) attached. squid_2_googleDNS -- squid is asking the DNS servers from google (squid times out / not working) squid_2_totd -- squid is asking the NDS server running totd (squid fetches the web

Bug#604775: squid3: Can't access www.google.com when using bind as DNS server

Package: squid3 Version: 3.1.6-1.2 Severity: normal When using bind9 or the DNS servers from Microsoft I have the error (in cache.log): ipcacheParse: No Address records in response to 'www.google.com' I found that everything is working fine when using totd as the DNS server. totd itself is