This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nscd/15862] New: nscd doesn't cache record containing more than one IP address.
- From: "frimik at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 20 Aug 2013 14:52:58 +0000
- Subject: [Bug nscd/15862] New: nscd doesn't cache record containing more than one IP address.
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15862
Bug ID: 15862
Summary: nscd doesn't cache record containing more than one IP
address.
Product: glibc
Version: 2.18
Status: NEW
Severity: normal
Priority: P2
Component: nscd
Assignee: unassigned at sourceware dot org
Reporter: frimik at gmail dot com
CC: drepper.fsp at gmail dot com
http://sourceware.org/git/?p=glibc.git;a=blob;f=nscd/hstcache.c;h=0d421fcbbb5e8823b660973e08b73e15e0dac3c8;hb=HEAD#l240
explains:
240 /* If the record contains more than one IP address (used for
241 load balancing etc) don't cache the entry. This is something
242 the current cache handling cannot handle and it is more than
243 questionable whether it is worthwhile complicating the cache
244 handling just for handling such a special case. */
This is hardly such a special case anymore. DNS round-robin is more and more
common... An example service today which use it extensively is AWS for example
for all of its S3 hosts ...
Is this as complicated to fix as it sounds? Would really appreciate a patch for
v2.12 (or later).
--
You are receiving this mail because:
You are on the CC list for the bug.