mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rob de Wit <>
Subject: [musl] Clarification on the NOERROR resolving choices
Date: Tue, 27 Jun 2023 07:12:51 -0700	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]


I ran into some issues lately and found this in the mailing list archive

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.

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.

Right now our options are:

   - adjusting ndots in resolv.conf - but we actually use the search path
   - 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
   - not to do it again (adding wildcard for something other than A or AAAA

Met vriendelijke groet / Kind regards

*Rob de Wit*

[-- Attachment #2: Type: text/html, Size: 2067 bytes --]

             reply	other threads:[~2023-06-27 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 14:12 Rob de Wit [this message]
2023-06-27 14:36 ` Rich Felker
2023-06-27 15:05   ` Rob de Wit
2023-06-27 15:22     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \

* 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

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).