From: Mark Hills <mark@xwax.org>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] DNS resolver fails prematurely when server reports failure?
Date: Wed, 1 Dec 2021 15:57:48 +0000 (GMT) [thread overview]
Message-ID: <2112011543340.2497@stax.localdomain> (raw)
In-Reply-To: <20211201152311.GF7074@brightrain.aerifal.cx>
On Wed, 1 Dec 2021, Rich Felker wrote:
> On Wed, Dec 01, 2021 at 12:49:07PM +0000, Mark Hills wrote:
> > 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?
>
> No. ServFail is an inconclusive response, treated basically the same
> as if no packet had arrived at all. (Slight difference: it triggers
> immediate retry up to a limited number of times.)
Ok, thanks. That sounds correct, and I realise now that the real process
of the query is in this source file [1] which is why the code looked so
opaque.
Could it be better to make a small change to the wiki text? Perhaps
"conclusive answer" instead of "response":
accepts whichever conclusive answer arrives first
> > And indeed this seems to be the behaviour we experience, as removing
> > 1.1.1.1 restored reliability.
>
> Have you looked at a packet capture of what's happening? Likely
> 1.1.1.1 was returning a false conclusive result (NxDomain or NODATA)
> rather than ServFail.
We caught the problem with a tcpdump (which is first how we realised the
differing behaviour between the man page and musl), and reproduced it with
"dig", however it doesn't seem to be reproducable now. My recollection is
that was an instant response and where I first encountered "ServFail" but
I'll see if we have logged the actual run. I'm _fairly_ sure I'd have
noticed a false but conclusive response.
I'm re-adding the "backup" DNS on a test system to see if we can get back
to reproducing the problem.
[1] https://git.musl-libc.org/cgit/musl/tree/src/network/res_msend.c#n30
Thanks
--
Mark
prev parent reply other threads:[~2021-12-01 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 12:49 Mark Hills
2021-12-01 15:23 ` Rich Felker
2021-12-01 15:57 ` Mark Hills [this message]
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=2112011543340.2497@stax.localdomain \
--to=mark@xwax.org \
--cc=dalias@libc.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).