Squid compiles with --disable-internal-dns on AMD64 since version 2.5.5-r2. I have tested Squid 2.5STABLE11 with --enable-internal-dns (default) on several very busy (480 clients on 25 Mbit) AMD64 machines (multilib and -multilib) and it works properly with better performance. Please consider removing --disable-internal-dns when USE=amd64. I just commented out line use amd64 && myconf="${myconf} --disable-internal-dns " in the ebuild. Reproducible: Always Steps to Reproduce:
isn't it better to handle DNS in the proper daemon (e.g. named)? that way all other programs could benefit from its cache as well.
(In reply to comment #1) > isn't it better to handle DNS in the proper daemon (e.g. named)? that way all > other programs could benefit from its cache as well. When you use squid with --disable-internal-dns it starts dnsserver processes by default. When you have a busy cache you must set maximum number of dnsserver children (35 processes) to fulfil client requests. Otherwise Squid would spam cache.log with the request to increase number of dns children. With --enable-internal-dns (default option) and properly DNS system setup, Squid uses DNS server specified in /etc/resolv.conf (tested) and therefore use existing DNS cache (DJBDNS in my case).
arch team, can you test net-proxy/squid-2.5.11 without --disable-internal-dns? eradicator added this in changelog: 24 Jun 2004; Jeremy Huddleston <eradicator@gentoo.org> squid-2.5.5-r2.ebuild: Marked ~amd64. amd64 needs --disable-internal-dns to run properly.
This compiles and works just fine here too, although I don't have a 25MBit pipe and that many clients to test it on :) I have removed the line as I can see no reason to keep it, although I don't think it warrants a revision bump. Please let me know if there are any further issues.
