Re: getaddrinfo error for existing host without requested address family
Date: Tue, 27 Sep 2022 22:41:06 UTC
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.