From: Shiz <hi@shiz.me>
To: musl@lists.openwall.com
Cc: yuri.kanivetsky@gmail.com
Subject: Re: [musl] getaddrinfo() fails for domains with no AAAA records (regression?)
Date: Mon, 19 Jul 2021 21:29:39 +0200 [thread overview]
Message-ID: <B0AC64E9-EFF0-43D2-AB56-F8C7C3AE53A6@shiz.me> (raw)
In-Reply-To: <CAMhVC3bCYs1QjM8xjFtTbsi-QQrjxiv0tuFxxwK=WKPwSacFfA@mail.gmail.com>
> On 19 Jul 3 Reiwa, at 20:51, Yuri Kanivetsky <yuri.kanivetsky@gmail.com> wrote:
>
> So you're saying that that is the registrar's fault (which also
> provides the name servers)? Can you possibly tell how this can be
> fixed? Other than by giving up on wildcard dns records?
Your registrar should return empty data responses if the domain exists,
but no records of the requested type are available for it. This is a
distinct response from the NXDOMAIN error response, which indicates
the domain doesn’t exist at all. This is specified by RFC1035[0] and
clarified further by RFC8020[1].
Appropriately, musl aborts the query if it gets such a response from the server[2].
The fact that it returns NXDOMAIN for AAAA-type queries if A-type record do in fact
exist would point to a bug in your registrar’s DNS implementation to me.
- Shiz
[0]: https://datatracker.ietf.org/doc/html/rfc1035 §4.1.1
[1]: https://datatracker.ietf.org/doc/html/rfc8020
[2]: https://git.musl-libc.org/cgit/musl/tree/src/network/res_msend.c?id=6a209f14ff7273d9429e5153c5b6b1990cb508e3#n149 (3 means NXDOMAIN)
next prev parent reply other threads:[~2021-07-19 19:29 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 [this message]
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
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=B0AC64E9-EFF0-43D2-AB56-F8C7C3AE53A6@shiz.me \
--to=hi@shiz.me \
--cc=musl@lists.openwall.com \
--cc=yuri.kanivetsky@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).