This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicatename service errors
- From: Jim Rees <rees at umich dot edu>
- To: David Howells <dhowells at redhat dot com>
- Cc: jmorris at namei dot org, keyrings at linux-nfs dot org, linux-nfs at vger dot kernel dot org,linux-security-module at vger dot kernel dot org, linux-kernel at vger dot kernel dot org,linux-cifs at vger dot kernel dot org, linux-api at vger dot kernel dot org,libc-alpha at sourceware dot org
- Date: Wed, 8 Feb 2012 09:15:52 -0500
- Subject: Re: [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicatename service errors
- References: <20120208122905.8902.65762.stgit@warthog.procyon.org.uk><20120208122917.8902.78395.stgit@warthog.procyon.org.uk>
David Howells wrote:
Define ENAMEUNKNOWN to indicate "Network name unknown". This can be used to
indicate, for example, that an attempt was made by dns_query() to make a query,
but the name server (e.g. a DNS server) replied indicating that it had no
matching records.
Would this be the same as NXDOMAIN? That is, does it mean the name server
couldn't find a record, or does it mean that the record doesn't exist?