[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 27 Jun 2023 10:36:04 -0400
From: Rich Felker <dalias@...c.org>
To: Rob de Wit <rob.dewit@...sto.com>
Cc: musl@...ts.openwall.com
Subject: Re: Clarification on the NOERROR resolving choices
On Tue, Jun 27, 2023 at 07:12:51AM -0700, Rob de Wit wrote:
> Hi
>
> I ran into some issues lately and found this in the mailing list archive
> https://www.openwall.com/lists/musl/2019/05/30/3
>
> The problem I had was with Alpine containers that suddenly failed resolving
> any hostname. I ended up tracing it back to a change I made in a domain
> that was in the "search" fiels in /etc/resolv.conf. The change was a
> wildcard TXT field. So when the resolver was resolving
> <host>.<tld>.<searchdomain>.<tld> it received an NOERROR reply. This
> indicates there is a record but just not a "A" or "AAAA" one. Perfectly
> valid as far as I know, but the resolver then quits the search.
This is the intended behavior. When reaching a name that exists, the
search stops and uses that result. Otherwise the search outcome will
be unstable depending on factors like which address family was
queried. In theory, that particular case could be precluded by always
performing both A and AAAA queries, even when only one was requested
by the caller, but users would likely not be happy with this behavior,
especially if it meant waiting for an uncached AAAA result that's not
even desired or erroring out in sloppy IPv4-only environments where
something is setup to make the AAAA fail. But not even getting into
that specific case, it's just having consistent high level semantics.
Search continues if and only if the attempted name does not exist.
> Maybe someone here can clarify this behaviour, because from the referred
> thread in the mailing list I get that this is caused by malfunctioning DNS,
> but in my case I don't think it is.
It's not "malfunctioning", just returning something whose semantics
mismatch what you want.
> Right now our options are:
>
> - adjusting ndots in resolv.conf - but we actually use the search path
Setting ndots greater than 1 always gives undesirable behaviors like
adding potentially substantial delay when looking up a name that was
already fully qualified, independently of whether you're using musl or
something else. It really should be treated only as a way to support
legacy setups, not part of new designs.
> - adding a dot at the end - this can only work if we know up front we
> don't want the search path
> - replacing Alpine with some libc-based image - this involves many
> changes
> - not to do it again (adding wildcard for something other than A or AAAA
> records)
It's not a matter of whether it's something other than A or AAAA; just
that you have a wildcard in your search domain path. This will never
give acceptable results unless your goal is to intercept all lookups
and have them return the same thing (either NODATA or a fixed
address).
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
