From nobody Tue Sep 27 22:41:06 2022
X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4McZNM4RLqz4d6Zc
	for <freebsd-net@mlmmj.nyi.freebsd.org>; Tue, 27 Sep 2022 22:41:07 +0000 (UTC)
	(envelope-from freebsd@dukhovni.org)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits))
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4McZNM0Kv1z3CJN
	for <freebsd-net@freebsd.org>; Tue, 27 Sep 2022 22:41:07 +0000 (UTC)
	(envelope-from freebsd@dukhovni.org)
Received: by straasha.imrryr.org (Postfix, from userid 1001)
	id 9F73311441D; Tue, 27 Sep 2022 18:41:06 -0400 (EDT)
Date: Tue, 27 Sep 2022 18:41:06 -0400
From: Viktor Dukhovni <freebsd@dukhovni.org>
To: freebsd-net@freebsd.org
Subject: Re: getaddrinfo error for existing host without requested address
 family
Message-ID: <YzN8AgkDvCWV9jaw@straasha.imrryr.org>
Reply-To: freebsd-net@freebsd.org
References: <202209272053.28RKrDEa004321@mail.karels.net>
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-net
List-Help: <mailto:freebsd-net+help@freebsd.org>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Subscribe: <mailto:freebsd-net+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-net+unsubscribe@freebsd.org>
Sender: owner-freebsd-net@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <202209272053.28RKrDEa004321@mail.karels.net>
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
X-Rspamd-Queue-Id: 4McZNM0Kv1z3CJN
X-Spamd-Bar: ++
Authentication-Results: mx1.freebsd.org;
	dkim=none;
	dmarc=none;
	spf=pass (mx1.freebsd.org: domain of freebsd@dukhovni.org designates 100.2.39.101 as permitted sender) smtp.mailfrom=freebsd@dukhovni.org
X-Spamd-Result: default: False [2.00 / 15.00];
	REPLYTO_EQ_TO_ADDR(5.00)[];
	NEURAL_HAM_MEDIUM(-1.00)[-0.998];
	NEURAL_HAM_SHORT(-0.99)[-0.994];
	NEURAL_HAM_LONG(-0.50)[-0.504];
	R_SPF_ALLOW(-0.20)[+ip4:100.2.39.101:c];
	RCVD_IN_DNSWL_MED(-0.20)[100.2.39.101:from];
	MIME_GOOD(-0.10)[text/plain];
	MLMMJ_DEST(0.00)[freebsd-net@freebsd.org];
	ASN(0.00)[asn:701, ipnet:100.2.0.0/16, country:US];
	FROM_EQ_ENVFROM(0.00)[];
	R_DKIM_NA(0.00)[];
	MIME_TRACE(0.00)[0:+];
	ARC_NA(0.00)[];
	GREYLIST(0.00)[pass,body];
	FROM_HAS_DN(0.00)[];
	HAS_REPLYTO(0.00)[freebsd-net@freebsd.org];
	RCVD_TLS_LAST(0.00)[];
	TO_MATCH_ENVRCPT_ALL(0.00)[];
	DMARC_NA(0.00)[dukhovni.org];
	TO_DN_NONE(0.00)[];
	RCPT_COUNT_ONE(0.00)[1];
	RCVD_COUNT_TWO(0.00)[2]
X-ThisMailContainsUnwantedMimeParts: N

On Tue, Sep 27, 2022 at 03:53:12PM -0500, Mike Karels wrote:

> The first error message is misleading, because the name *does* resolve,
> but has no AAAA record, and it is the same error message as for a name
> that truly does not exist.

FWIW, the distinction between NODATA and NXDOMAIN is these days not
infrequently violated at the authoritative nameserver:

    https://datatracker.ietf.org/doc/html/draft-valsorda-dnsop-black-lies-00

So whether or not a name actually exists or just fails to have the
requested record type is at times not easily determined. :-(

-- 
    Viktor.