Re: [squid3-ipv6] dns_internal.cc

Rafael Martinez (Squid development) wrote:
> The lasts tests on SNMP seems to work when --disable-dns-internal
>
> I gues there is a typo around dns_internal.cc
>
>
> #if USE_IPV6
> if(q->need_A && (Config.onoff.dns_require_A == 1 || n <= 0 ) )
> {
> /* ERROR or NO AAAA exist. Failover to A records. */
>
> imasd.ipv6.elmundo.es will fire an error, even with n=4 ...

which error ?

>
> host -t AAAA imasd.ipv6.elmundo.es
> imasd.ipv6.elmundo.es has IPv6 address 2001:450:9:10::115
> imasd.ipv6.elmundo.es has IPv6 address 2001:800:400:10::71
> imasd.ipv6.elmundo.es has IPv6 address 2001:800:400:10::115
> imasd.ipv6.elmundo.es has IPv6 address 2001:450:9:10::71
>
>
> Should it be fixed to ? recall the && instead of || .
> ---
>> if(q->need_A && (Config.onoff.dns_require_A == 1 && n <= 0 ) )

No. I initially had it with two &&. But it turns out that when IPv6 are
provided but not working we need to be able to fallback to the IPv4.
That is getting rarer, but still may occur due to any number of network
issues.
If the IPv4 are not placed into cache at the time of lookup squid trusts
its existing (v6) results and returns a false-error page.

... getting on and commenting the code to that effect ...

>
> Even with that, ipcache.cc seems to have problems with canonical
> names...

Any more detail on what those problems are?
I have seen some weird behaviour listing ipcache, but nothing I have
been able to track down yet. If you can provide any light all the
better. My bug has something to do with walking the hash list under some
still unknown conditions.

>
> For the time beeing, I will compile squid3-ipv6 with
> --disable-dns-internal...
>

Amos
Received on Mon Nov 26 2007 - 03:15:05 MST