From: Mark Hills <mark@xwax.org>
To: musl@lists.openwall.com
Subject: [musl] DNS resolver fails prematurely when server reports failure?
Date: Wed, 1 Dec 2021 12:49:07 +0000 (GMT) [thread overview]
Message-ID: <2112011203500.21490@stax.localdomain> (raw)
With multiple DNS servers in /etc/resolv.conf, the docs [1] are clear:
"musl's resolver queries them all in parallel and accepts whichever
response arrives first."
So dual configuration is expected to give greater resiliancy:
nameserver 213.186.33.99 # OVH
nameserver 1.1.1.1 # Cloudflare
However, 1.1.1.1 appears quite prone to some kind of internal SERVFAIL
(may be internal load shedding; though we are not making excessive DNS
queries)
With glibc's cascading behaviour (or perhaps another OS) this may be dealt
with by the client.
But if the wiki is read literally, the first response received is "this
server has failed" then a good response from another server is ignored?
And indeed this seems to be the behaviour we experience, as removing
1.1.1.1 restored reliability.
I tried to confirm this in the source [2] but found I'd need more time to
understand this code.
Also, diagnosis was made more difficult by a colleage diligently following
the resolv.conf(5) man page on the host (installed via man-pages on Alpine
Linux) but this documents glibc. Perhaps musl could/should provide its
own, but I expect there is a policy for this and similar issues.
Thanks
[1] https://wiki.musl-libc.org/functional-differences-from-glibc.html
[2] https://git.musl-libc.org/cgit/musl/tree/src/network/lookup_name.c#n296
--
Mark
next reply other threads:[~2021-12-01 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 12:49 Mark Hills [this message]
2021-12-01 15:23 ` Rich Felker
2021-12-01 15:57 ` Mark Hills
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=2112011203500.21490@stax.localdomain \
--to=mark@xwax.org \
--cc=musl@lists.openwall.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).