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=-1.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,PDS_OTHER_BAD_TLD,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 20612 invoked from network); 19 Jul 2021 19:54:05 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 19 Jul 2021 19:54:05 -0000 Received: (qmail 1882 invoked by uid 550); 19 Jul 2021 19:54:03 -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 1864 invoked from network); 19 Jul 2021 19:54:03 -0000 X-Virus-Scanned: Debian amavisd-new at disroot.org Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1626724430; bh=dk012KGLErsiPjIYEzmGcULTM/5U/g7oG+Mhrg6n6gI=; h=To:Subject:From:Date:In-Reply-To; b=F7iSMgiZiZXrjmATBnqMLOuRHDEAn10tyW80Gf89BXXRiiD+ryt7Ii/IVA6X53/yV VecHc8WzaChcD3eSFkHfw2AerFZF1acZdzG/nFUwVLXxr3dq00fmXFkTlFMvj2V+Ah 1FXG0vbveqspM7kcITW6pI5T2mppR9DkAlSZS46Atveg882Q6wlKDo9Pn6MynIRVwL +SdxuqFLE1GtHe03/jiEYB9OnVmJwHwZlQLmr4lM/VQkfsYvrwSetNU2h/gYTgk025 fkm8h4iaqhAWq5V3JnrAZ2tYiIBFVhnfHDVf5yMrUuqnCsRavVyfeMUShZMOkGXfyj bma0gTtwij/xQ== Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 To: , "Florian Weimer" From: =?utf-8?q?=C3=89rico_Nogueira?= Date: Mon, 19 Jul 2021 16:47:23 -0300 Message-Id: In-Reply-To: Subject: Re: [musl] getaddrinfo() fails for domains with no AAAA records (regression?) On Mon Jul 19, 2021 at 3:51 PM -03, Yuri Kanivetsky wrote: > So you're saying that that is the registrar's fault (which also > provides the name servers)? Can you possibly tell how this can be > fixed? Other than by giving up on wildcard dns records? > > A couple more points. First, apparently there was some change between > musl-1.2.2-r0 and musl-1.1.24-r10, getaddrinfo() stops working since fd7ec068efd590c0393a612599a4fab9bb0a8633 and 5cf1ac2443ad0dba263559a3fe043d929e0e5c4c have happened between those. It's possible 5cf1ac applies to your case, since it changes the error handling to take NXDOMAIN into account from any of the queries. > Alpine Linux 3.13. Which comes down to the fact that ping and ssh > can't resolve such hostnames. Although host, getent and dig can. AFAIK dig/drill will look at /etc/resolv.conf for nameservers, but use their own resolver, not libc's. getent, on the other hand, uses the libc resolver, so comparing how ssh/ping and getent perform the query might be worthwhile, since they are all using the same resolvers. > Second, it works on Arch Linux, Debians 8, 9, 10, and CentOS 7. The > way it looks, it works on libc, and doesn't work on musl. *glibc > > Additionally I've attached the relevant part of the registrars' web > interface. > > Regards, > Yuri > > On Mon, Jul 19, 2021 at 4:22 PM Florian Weimer > wrote: > > > > * Yuri Kanivetsky: > > > > > $ docker run --rm -itv $PWD:/app alpine:3.14 ./app/a.sh > > > ... > > > + ./a.out p2.x-yuri.site set_ai_family > > > AF_INET: 3.67.126.242 > > > + ./a.out p2.x-yuri.site > > > getaddrinfo: Name does not resolve > > > > p2.x-yuri.site/IN/AAAA queries result in Name Error/NXDOMAIN, so the > > domain is misconfigured. This error is independent of the record type. > > > > Thanks, > > Florian > >