Bug 742680 - squid ipv6: built-in dns resolver incapable of rfc3484
Summary: squid ipv6: built-in dns resolver incapable of rfc3484
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: squid
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiri Skala
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-01 10:13 UTC by Frank Ch. Eigler
Modified: 2014-11-09 22:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-21 08:42:59 UTC
Type: ---


Attachments (Terms of Use)

Description Frank Ch. Eigler 2011-10-01 10:13:16 UTC
Squid includes a dns resolver for some reason, and has no configuration
option to use the plain glibc resolver.  So it's stuck with less complete
implementation, notably one that lacks RFC3484 (/etc/gai.conf) support
for locally administered ipv6/ipv4 address prioritization.

This is a problem when one has a relatively poor ipv6 setup (tunneled
perhaps), or when a dual-homed (ipv4+ipv6) web server has much worse
performance over the latter than the former.  Squid's hard-coded
attitude favouring ipv6 causes poor/broken connections to e.g. youtube.

See also: http://bugs.squid-cache.org/show_bug.cgi?id=3086

Please consider carrying the patch suggested in that bug, or perhaps
prevailing upon the squid upstream to apply the patch or have an
option for using the system resolver.

Comment 1 Jiri Skala 2011-10-03 08:11:45 UTC
The patch isn't included into nightly Squid-3.2 by upstream yet ...

Comment 2 Frank Ch. Eigler 2011-10-03 13:00:49 UTC
> The patch isn't included into nightly Squid-3.2 by upstream yet ...

Yeah, I realize that.  I get the impression that the squid developers are
not very sympathetic to non-ipv6 concerns.

Comment 3 Frank Ch. Eigler 2011-11-19 02:58:40 UTC
It appears that http://kojipkgs.fedoraproject.org/packages/squid/3.2.0.13/5.fc16/x86_64/squid-3.2.0.13-5.fc16.x86_64.rpm fixes this problem, with the "dns_v4_first" configuration option added.


Note You need to log in before you can comment on or make changes to this bug.