[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <17614.1328781889@redhat.com>
Date: Thu, 09 Feb 2012 10:04:49 +0000
From: David Howells <dhowells@...hat.com>
To: Jim Rees <rees@...ch.edu>
Cc: dhowells@...hat.com, 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
Jim Rees <rees@...ch.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
--
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