public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "brunni at netestate dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/17215] New: getaddrinfo with AI_CANONNAME and AF_INET causes PTR lookup Date: Wed, 30 Jul 2014 14:00:00 -0000 [thread overview] Message-ID: <bug-17215-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17215 Bug ID: 17215 Summary: getaddrinfo with AI_CANONNAME and AF_INET causes PTR lookup Product: glibc Version: 2.17 Status: NEW Severity: normal Priority: P2 Component: network Assignee: unassigned at sourceware dot org Reporter: brunni at netestate dot de getaddrinfo makes a PTR lookup when called with ai_flags = AI_CANONNAME and ai_family = AF_INET: #include <sys/types.h> #include <sys/socket.h> #include <netdb.h> struct addrinfo hints = {.ai_flags = AI_CANONNAME, .ai_family = AF_INET}; int main (int argc, char *argv[]) { struct addrinfo *ap; int err; err = getaddrinfo("netestate.de", "500", &hints, &ap); } This is problematic for me as Javas InetAddress.getByName() works like this on ipv4 systems and causes an unnecessary reverse lookup for every forward lookup. It seems to be fixed in current distributions: https://bugzilla.redhat.com/show_bug.cgi?id=714823 I get the problem when using glibc 2.17 compiled from source. Is this still an issue with glibc 2.19? -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-07-30 14:00 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-30 14:00 brunni at netestate dot de [this message] 2014-08-04 8:12 ` [Bug network/17215] " schwab@linux-m68k.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-17215-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).