.\" NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
.\" WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.\" $Id: lwres.3,v 1.7 2000/11/18 02:59:12 bwelling Exp $
+.\" $Id: lwres.3,v 1.8 2000/12/04 18:37:35 gson Exp $
.Dd Jun 30, 2000
.Dt LWRES 3
and address-to-hostname lookup services to applications by
transmitting lookup requests to a resolver daemon
.Nm lwresd
-running on the local host. The resover daemon performs the
+running on the local host. The resover daemon performs the
lookup using the DNS or possibly other name service protocols,
and returns the results to the application through the library.
The library and resolver daemon communicate using a simple
These may be called by applications that require more detailed
control over the lookup process than the standard functions
provide.
+.Pp
+In addition to these name service independent address lookup
+functions, the library implements a new, experimental API
+for looking up arbitrary DNS resource records, using the
+.Fn lwres_getaddrsbyname
+function.
+.Pp
Finally, there is a low-level API for converting lookup
requests and responses to and from raw lwres protocol packets.
This API can be used by clients requiring nonblocking operation,
.\" NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
.\" WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.\" $Id: lwres_config.3,v 1.4 2000/11/18 02:59:40 bwelling Exp $
+.\" $Id: lwres_config.3,v 1.5 2000/12/04 18:37:37 gson Exp $
.Dd Jun 30, 2000
.Dt LWRES_CONFIG 3
If this happens, the function returns
.Er LWRES_R_FAILURE .
.Sh SEE ALSO
-.Xr stdio 3,
+.Xr stdio 3 ,
.Xr resolver 5 .
.Sh FILES
.Pa /etc/resolv.conf
.\" NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
.\" WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.\" $Id: lwres_gethostent.3,v 1.5 2000/11/18 03:00:21 bwelling Exp $
+.\" $Id: lwres_gethostent.3,v 1.6 2000/12/04 18:37:38 gson Exp $
.Dd Jun 30, 2000
.Dt LWRES_GETHOSTENT 3
.Fn lwres_gethostbyaddr_r
respectively.
.Pp
-Although the above functions can be considered as drop-in replacements
-for their equivalents in the system software, there are limitations.
-The functions that are documented here only use the BIND9 lighweight
-resolver daemon
-That implies that they only use the DNS for host and address lookups.
-Therefore these functions do not perform lookups in
+The resolver daemon does not currently support any non-DNS
+name services such as
.Pa /etc/hosts
-or in
-.Dv NIS/YP
or
-.Dv NIS+
-maps which could be supported by the operating system's
-.Xr gethostent 3
-functions.
+.Dv NIS ,
+consequently the above functions don't, either.
.\" NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
.\" WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.\" $Id: lwres_getnameinfo.3,v 1.6 2000/11/18 03:00:28 bwelling Exp $
+.\" $Id: lwres_getnameinfo.3,v 1.7 2000/12/04 18:37:39 gson Exp $
.Dd Jun 30, 2000
.Dt LWRES_GETNAMEINFO 3
.Xr getservbyport 3 ,
.Xr lwres 3 ,
.Xr lwres_getnameinfo 3 ,
-.Xr lwres_getnamebyaddr 3,
+.Xr lwres_getnamebyaddr 3 .
.Xr lwres_net_ntop 3 .
.Sh BUGS
RFC2133 fails to define what the nonzero return values of
.\" NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
.\" WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.\" $Id: lwres_hstrerror.3,v 1.4 2000/11/18 03:00:41 bwelling Exp $
+.\" $Id: lwres_hstrerror.3,v 1.5 2000/12/04 18:37:40 gson Exp $
.Dd Jun 30, 2000
.Dt LWRES_ERROR 3
\*qUnknown server error\*q
.It Li NO_DATA
\*qNo address associated with name\*q
+.El
.Sh RETURN VALUES
The string \*qUnknown resolver error\*q is returned by
.Fn lwres_hstrerror
.\" NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
.\" WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.\" $Id: lwres.3,v 1.7 2000/11/18 02:59:12 bwelling Exp $
+.\" $Id: lwres.3,v 1.8 2000/12/04 18:37:35 gson Exp $
.Dd Jun 30, 2000
.Dt LWRES 3
and address-to-hostname lookup services to applications by
transmitting lookup requests to a resolver daemon
.Nm lwresd
-running on the local host. The resover daemon performs the
+running on the local host. The resover daemon performs the
lookup using the DNS or possibly other name service protocols,
and returns the results to the application through the library.
The library and resolver daemon communicate using a simple
These may be called by applications that require more detailed
control over the lookup process than the standard functions
provide.
+.Pp
+In addition to these name service independent address lookup
+functions, the library implements a new, experimental API
+for looking up arbitrary DNS resource records, using the
+.Fn lwres_getaddrsbyname
+function.
+.Pp
Finally, there is a low-level API for converting lookup
requests and responses to and from raw lwres protocol packets.
This API can be used by clients requiring nonblocking operation,
.\" NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
.\" WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.\" $Id: lwres_config.3,v 1.4 2000/11/18 02:59:40 bwelling Exp $
+.\" $Id: lwres_config.3,v 1.5 2000/12/04 18:37:37 gson Exp $
.Dd Jun 30, 2000
.Dt LWRES_CONFIG 3
If this happens, the function returns
.Er LWRES_R_FAILURE .
.Sh SEE ALSO
-.Xr stdio 3,
+.Xr stdio 3 ,
.Xr resolver 5 .
.Sh FILES
.Pa /etc/resolv.conf
.\" NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
.\" WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.\" $Id: lwres_gethostent.3,v 1.5 2000/11/18 03:00:21 bwelling Exp $
+.\" $Id: lwres_gethostent.3,v 1.6 2000/12/04 18:37:38 gson Exp $
.Dd Jun 30, 2000
.Dt LWRES_GETHOSTENT 3
.Fn lwres_gethostbyaddr_r
respectively.
.Pp
-Although the above functions can be considered as drop-in replacements
-for their equivalents in the system software, there are limitations.
-The functions that are documented here only use the BIND9 lighweight
-resolver daemon
-That implies that they only use the DNS for host and address lookups.
-Therefore these functions do not perform lookups in
+The resolver daemon does not currently support any non-DNS
+name services such as
.Pa /etc/hosts
-or in
-.Dv NIS/YP
or
-.Dv NIS+
-maps which could be supported by the operating system's
-.Xr gethostent 3
-functions.
+.Dv NIS ,
+consequently the above functions don't, either.
.\" NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
.\" WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.\" $Id: lwres_getnameinfo.3,v 1.6 2000/11/18 03:00:28 bwelling Exp $
+.\" $Id: lwres_getnameinfo.3,v 1.7 2000/12/04 18:37:39 gson Exp $
.Dd Jun 30, 2000
.Dt LWRES_GETNAMEINFO 3
.Xr getservbyport 3 ,
.Xr lwres 3 ,
.Xr lwres_getnameinfo 3 ,
-.Xr lwres_getnamebyaddr 3,
+.Xr lwres_getnamebyaddr 3 .
.Xr lwres_net_ntop 3 .
.Sh BUGS
RFC2133 fails to define what the nonzero return values of
.\" NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
.\" WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.\" $Id: lwres_hstrerror.3,v 1.4 2000/11/18 03:00:41 bwelling Exp $
+.\" $Id: lwres_hstrerror.3,v 1.5 2000/12/04 18:37:40 gson Exp $
.Dd Jun 30, 2000
.Dt LWRES_ERROR 3
\*qUnknown server error\*q
.It Li NO_DATA
\*qNo address associated with name\*q
+.El
.Sh RETURN VALUES
The string \*qUnknown resolver error\*q is returned by
.Fn lwres_hstrerror
projects / thirdparty / bind9.git / commitdiff
