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/11709] glibc domain resolution does not obtain IP addresses from truncated UDP DNS responses.
Date: Wed, 16 Jun 2010 21:11:00 -0000	[thread overview]
Message-ID: <20100616211054.2271.qmail@sourceware.org> (raw)
In-Reply-To: <20100616132818.11709.khanipov@gmail.com>


------- Additional Comments From pasky at suse dot cz  2010-06-16 21:10 -------
Thanks for your report - though its form is more of a blog post and more
to-the-point summary would be easier to process.

As you note, the router behavior is completely non-standard. However, we cannot
just decide we do not need anything else from the DNS record, since it may be
crucial to get all the records e.g. to properly sort and choose the appropriate
IP address based on the preferred family and scope; getaddrinfo() supports
complex ordering mechanisms for this (see gai.conf(5)). Ignoring the rest of a
truncated reply would cause invalid behavior.

Thus, even if we introduced a special option to process even truncated UDP
replies, that behavior would be actually harmful and it is better then to use a
different (e.g. local-running) caching nameserver. Since this is the first bug
report about this router I have ever seen, I don't think your problem is that
wide-spread; but even if it was, it would be much better for the distributions
to test and handle such broken DNS servers specially (e.g. as part of the DHCP
negotiation), falling back to a local caching nameserver instead of forcing
glibc to process broken DNS replies at all costs.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX


http://sourceware.org/bugzilla/show_bug.cgi?id=11709

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2010-06-16 21:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 13:28 [Bug libc/11709] New: " khanipov at gmail dot com
2010-06-16 21:11 ` pasky at suse dot cz [this message]
2010-06-17  4:18 ` [Bug libc/11709] " khanipov at gmail dot com
     [not found] <bug-11709-131@http.sourceware.org/bugzilla/>
2014-06-30 17:47 ` 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=20100616211054.2271.qmail@sourceware.org \
    --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: link
Be 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).