- Subject: Re: [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate name service errors
- From: David Howells <dhowells@xxxxxxxxxx>
- Date: Thu, 09 Feb 2012 10:04:49 +0000
- Cc: dhowells@xxxxxxxxxx, jmorris@xxxxxxxxx, keyrings@xxxxxxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx, linux-security-module@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-cifs@xxxxxxxxxxxxxxx, linux-api@xxxxxxxxxxxxxxx, libc-alpha@xxxxxxxxxxxxxx
- In-reply-to: <20120208141552.GA3273@umich.edu>
- Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903
- References: <20120208141552.GA3273@umich.edu> <20120208122905.8902.65762.stgit@warthog.procyon.org.uk> <20120208122917.8902.78395.stgit@warthog.procyon.org.uk>
Jim Rees <rees@xxxxxxxxx> 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-api" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Home]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Free Online Dating]
[Linux Kernel]
[Linux SCSI]
[XFree86]