public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dos at scarff dot id.au" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/11950] res_send fails with ETIMEDOUT on successful DNS UPDATE Date: Sat, 19 Oct 2013 23:49:00 -0000 [thread overview] Message-ID: <bug-11950-131-pO0wy1qf2v@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-11950-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=11950 --- Comment #4 from Dean Scarff <dos at scarff dot id.au> --- Thanks Florian - I realize it's a little optimistic expecting the resolver library to work for non-QUERY messages. However, I think there's already some separation in the resolver's high-level routines (res_query and res_search) and res_send; the latter seems intended to be message-agnostic. I think it's valuable for users of glibc if res_send can preserve its generality - and doing so here is a small change. Please consider this patch. :) For portability I ended up implementing my own code for sending DNS messages over sockets (years ago - this is quite an old bug!), just as you suggested. But it's a shame since it duplicates much of the functionality already present in most implementations of res_send. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-19 23:49 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-11950-131@http.sourceware.org/bugzilla/> 2012-02-21 1:51 ` jsm28 at gcc dot gnu.org 2012-12-19 10:45 ` schwab@linux-m68k.org 2013-10-18 11:38 ` fweimer at redhat dot com 2013-10-19 23:49 ` dos at scarff dot id.au [this message] 2013-10-21 7:18 ` neleai at seznam dot cz 2013-10-21 7:20 ` fweimer at redhat dot com 2013-10-23 13:11 ` neleai at seznam dot cz 2014-06-30 8:10 ` 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-11950-131-pO0wy1qf2v@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).