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 indicate name service errors
- From: David Howells <dhowells at redhat dot com>
- To: Jim Rees <rees at umich dot edu>
- Cc: dhowells at redhat dot com, 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: Thu, 09 Feb 2012 10:04:49 +0000
- Subject: Re: [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate name service errors
- References: <20120208141552.GA3273@umich.edu> <20120208122905.8902.65762.stgit@warthog.procyon.org.uk> <20120208122917.8902.78395.stgit@warthog.procyon.org.uk>
Jim Rees <rees@umich.edu> 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?
Is there a way to tell the difference? Can you store a negative record in the
DNS? Or is it that the DNS has records for the name, just not records of the
type you're looking for (eg. NO_ADDRESS/NO_DATA from gethostbyname())?
David