From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 25749 invoked from network); 27 Jun 2023 14:13:09 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 27 Jun 2023 14:13:09 -0000 Received: (qmail 3520 invoked by uid 550); 27 Jun 2023 14:13:04 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 3481 invoked from network); 27 Jun 2023 14:13:03 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coosto.com; s=google2; t=1687875172; x=1690467172; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=cwGGnKMV8c4ziCCxLPPPYy4RXaQ3oaXmam6vo2gAh84=; b=dT/TnDbKNHKbBaywRW0FzqL9XbX+CD+hR9+NQuKGr4Gbxj/X54t8TQDxLh5M4T+6iN GH4ky7JrKUEvZQdqMDE06SaWLBWTBulbPD+M7dBoH0ld529clamuzvLdD4J4pSDObmy8 5RiAAYsIVwt5ULFTAg1ZhQZKgFd6S9JXRKohTIaEn4wc78GWluk1uT0asc0cq7LI1Isb USBNeBR5iCoDjsfz+3WGHXXGJgI2jfpF+T57ZGMByuOsipPmwB6yA7zdt58BqdGyCtby p0CRsjnOoNFUfnmvKAipJIOoNxtkM2ck61L51bgaTVmG5txnZJFY7YCs1jq2r9OvDNmV H6Lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687875172; x=1690467172; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=cwGGnKMV8c4ziCCxLPPPYy4RXaQ3oaXmam6vo2gAh84=; b=gJUh19j9dNYpkWtLJvPcnpJYmTXPmCvPuoMkcxTdgQ6UzaSidASy53KWjBA1XJ1ArA slh4SKQ7XhI4us1CiuZqCQK4th7M75PaUY6AoOkH+osHIkbYqx7rv1C9nawIhkDIwXiv mF5IJNumIpCJGXhDBFVjGELXGNaAoRhrf8GE8EEbDGinN0lcxJ5wK1nng84fSGkm+kc1 d0qsod2tsqqc91hQCb8XV0Gky4xtxLf7dQg/DPAkQK690e2WGo0S5Dkcz/0unGB5K/gJ c6dMkNbirPAC6Em7r8cciI7ZcXQ7//ccLI94UqjPaS4gGgFyBhvdkKNRFO3fZ6cH/0JY U4ug== X-Gm-Message-State: AC+VfDxDk+Z0kJ+rFzHh8pqW3XjePhArBUgeTWVkt/2wgVG5o+b2Kzgw SR7UhjCwjfrCJxBEagSXlUdlLr3h9/ac67ya6xcQECRQjWBQK23x X-Google-Smtp-Source: ACHHUZ7GUgvyZLrMVk8gcw9t6E7muk/tX/NCrOXdQxbtC5qOZOHAnxsq/esXnnIsX2BWijR0w5jkoFY9k2qK0LAQezo= X-Received: by 2002:a2e:9e4f:0:b0:2b1:b4e9:4c3 with SMTP id g15-20020a2e9e4f000000b002b1b4e904c3mr21935881ljk.2.1687875172019; Tue, 27 Jun 2023 07:12:52 -0700 (PDT) Mime-Version: 1.0 (Mimestream 1.0.3) From: Rob de Wit Date: Tue, 27 Jun 2023 07:12:51 -0700 Message-ID: To: musl@lists.openwall.com Content-Type: multipart/alternative; boundary="0000000000000dc4f305ff1d1083" Subject: [musl] Clarification on the NOERROR resolving choices --0000000000000dc4f305ff1d1083 Content-Type: text/plain; charset="UTF-8" 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 ... 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 changes - not to do it again (adding wildcard for something other than A or AAAA records) Met vriendelijke groet / Kind regards *Rob de Wit* --0000000000000dc4f305ff1d1083 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

I ran into s= ome issues lately and found this in the mailing list archive=C2=A0https://www.openwall.= com/lists/musl/2019/05/30/3

The problem I had was with Alpine containers that suddenly failed res= olving any hostname. I ended up tracing it back to a change I made in a dom= ain that was in the "search" fiels in /etc/resolv.conf. The chang= e 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 "AAA= A" 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 ma= iling 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 invo= lves many changes
  • not to do it again (adding wildcard for something= other than A or AAAA records)


Met vriendelijke groet / Kind regards

Rob = de Wit=C2=A0
--0000000000000dc4f305ff1d1083--