From: Rich Felker <dalias@libc.org>
To: "Olivier A." <olivier.antoine@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] getaddrinfo() fails for domains with no AAAA records (regression?)
Date: Mon, 19 Jul 2021 17:12:25 -0400 [thread overview]
Message-ID: <20210719211225.GK13220@brightrain.aerifal.cx> (raw)
In-Reply-To: <5463e48e-c6b7-f6e3-e405-6cf654b35c57@gmail.com>
On Mon, Jul 19, 2021 at 11:07:21PM +0200, Olivier A. wrote:
> On 19/07/2021 14:58, Yuri Kanivetsky wrote:
> > [..]
>
> Hi,
>
> I notice that too. If both A and AAAA are sent and there is a
> response for A and NXDomain for AAAA
>
> musl-libc discard both results. It's the expected behaviour
> according to this commit:
>
> https://git.musl-libc.org/cgit/musl/commit/src/network/lookup_name.c?id=5cf1ac2443ad0dba263559a3fe043d929e0e5c4c
>
> And it conform to https://datatracker.ietf.org/doc/html/rfc8020
>
> It's was not the case before Alpine-Linux 3.13
>
> But I also notice that if the DNS reply ServFailed instead of
> NXDomain for AAAA request, musl-libc retry 10 times, return 'bad
> address' and do not fallback to return a A record.
>
> According to
> https://datatracker.ietf.org/doc/html/rfc4074#section-4.3 it's not
> expected.
This behavior is necessary/mandatory to provide secure behavior under
DNSSEC. Otherwise a forged response (causing ServFail) would result in
a false answer returned to the application, indicating that only one
or the other exists, rather than the correct inconclusive answer.
This is https://sourceware.org/bugzilla/show_bug.cgi?id=27929
next prev parent reply other threads:[~2021-07-19 21:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 12:58 Yuri Kanivetsky
2021-07-19 13:22 ` Florian Weimer
2021-07-19 18:51 ` Yuri Kanivetsky
2021-07-19 19:29 ` Shiz
2021-07-19 19:47 ` Érico Nogueira
2021-07-19 21:08 ` Rich Felker
2021-07-19 21:07 ` Olivier A.
2021-07-19 21:12 ` Rich Felker [this message]
2021-07-23 20:25 ` Yuri Kanivetsky
2021-07-23 20:33 ` Yuri Kanivetsky
2021-07-23 20:45 ` Laurent Bercot
2021-07-27 14:21 ` Yuri Kanivetsky
2021-07-27 14:41 ` Rich Felker
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=20210719211225.GK13220@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=olivier.antoine@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).