This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nscd/15862] nscd doesn't cache record containing more than one IP address.
- From: "aoliva at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 14 May 2014 08:11:39 +0000
- Subject: [Bug nscd/15862] nscd doesn't cache record containing more than one IP address.
- Auto-submitted: auto-generated
- References: <bug-15862-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15862
--- Comment #5 from Alexandre Oliva <aoliva at sourceware dot org> ---
Another thought that occurred to me was introducing in getaddrinfo a way to
query the nscd cache without performing a lookup if we don't have a cached
answer, before falling back to gethostbyname2_r, and performing a lookup proper
afterwards, if we don't fall back.
Some means to query the cache without a lookup on failure might enable us to
use GETAI cached values to satisfy GETHOSTBYNAME or GETHOSTBYNAME6 requests,
and perhaps vice-versa. Although the latter isn't necessarily right: given a
sequence of nss backends for hosts, if we find a result for say v6 with the
first backend, should we ever combine it with a result for v4 with later
backends? Should it matter whether we're looking for v4 addresses only? I'd
think not, and that if we find v6 addresses first, we should stop there and not
report any IPv4 addresses, but falling back to gethostbyname2_r doesn't behave
that way.
--
You are receiving this mail because:
You are on the CC list for the bug.