[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120208141552.GA3273@umich.edu>
Date: Wed, 8 Feb 2012 09:15:52 -0500
From: Jim Rees <rees@...ch.edu>
To: David Howells <dhowells@...hat.com>
Cc: jmorris@...ei.org, keyrings@...ux-nfs.org,
linux-nfs@...r.kernel.org, linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-cifs@...r.kernel.org,
linux-api@...r.kernel.org, libc-alpha@...rceware.org
Subject: Re: [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate
name service errors
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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists