public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pasky at suse dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/12684] New: Multi-request DNS lookups do not properly fall back to secondary nameserver Date: Tue, 19 Apr 2011 15:28:00 -0000 [thread overview] Message-ID: <bug-12684-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=12684 Summary: Multi-request DNS lookups do not properly fall back to secondary nameserver Product: glibc Version: 2.13 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper.fsp@gmail.com ReportedBy: pasky@suse.cz Created attachment 5678 --> http://sourceware.org/bugzilla/attachment.cgi?id=5678 proposed patch The resolver does not properly handle a case where AF_UNSPEC query is started, two requests are therefore dispatched, and something like NOTIMP or SERVFAIL is returned to one of them (e.g. AF_INET6). In this case, the second nameserver in queue is not queried even though it should be. It is caused by an omission of resplen = 0 in the appropriate branch of send_dg() - therefore, when checking whether next nameserver should be queried, it is assumed that a proper reply was received from the first one. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-04-19 15:28 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-19 15:28 pasky at suse dot cz [this message] 2011-05-31 2:53 ` [Bug libc/12684] " drepper.fsp at gmail dot com 2011-06-03 10:58 ` schwab@linux-m68k.org 2011-06-07 14:48 ` vapier at gentoo dot org 2011-06-16 2:45 ` drepper.fsp at gmail dot com 2014-02-16 18:23 ` jackie.rosen at hushmail dot com 2014-05-28 19:42 ` schwab at sourceware dot org 2014-06-27 13:31 ` fweimer at redhat dot com 2014-06-27 13:35 ` fweimer at redhat dot com
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-12684-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).