getdns/doc/libgetdns.3.in

.\" The "BSD-New" License
.\" 
.\" Copyright (c) 2013, Versign, Inc.
.\" All rights reserved.
.\" 
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions are met:
.\" * Redistributions of source code must retain the above copyright
.\"   notice, this list of conditions and the following disclaimer.
.\" * Redistributions in binary form must reproduce the above copyright
.\"   notice, this list of conditions and the following disclaimer in the
.\"   documentation and/or other materials provided with the distribution.
.\" * Neither the name of the <organization> nor the
.\"   names of its contributors may be used to endorse or promote products
.\"   derived from this software without specific prior written permission.
.\" 
.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
.\" DISCLAIMED. IN NO EVENT SHALL Verisign, Inc. BE LIABLE FOR ANY
.\" DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
.\" ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
.\" SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\" 

.TH libgetdns 3 "@date@" "getdns @version@" getdns
.SH NAME
libgetdns
.Sh LIBRARY
DNS Resolver library (libgetdns, -lgetdns)

.SH SYNOPSIS
.Lb libgetdns

This man page describes the getdns library, the general concepts behind the API and some of the common elements of the public interface to the library.  Each of the public entry points and more complex data types are captured in separate man pages.

.SH DESCRIPTION

.LP
getdns is modern asynchronous DNS API intended to be useful to application developers and operating system distributors as a way of making all types of DNS information easily available in many types of programs. The major features of this new API are:

.RS 3
    Full support for event-driven programming
    Supports DNSSEC in multiple ways
    Mirroring of the resolution in getaddrinfo()
    Easily supports all RRtypes, even those yet to be defined
.RE

.LP
Each of the entry points is offered with both asynchronous and synchronous signatures.  The asynchronous functions rely on event handling and callback via libevent.
Functions are thread safe.

.LP
A context structure maintains DNS query and response data and is used to maintain state during calls to the public entry points.

.SH EXTENSIONS

Applications may populate an extension dictionary when making a call to the public entry points.  To use an extension add it to the extension dictionary prior to making the call to the public entry point and set the value depending on the behavior you expect.  These extensions include:

.HP 3
dnssec_return_status (int)

Set to GETDNS_EXTENSION_TRUE to include the DNSSEC status for each DNS record in the replies_tree

.HP 3
dnssec_return_only_secure (int)

Set to GETDNS_EXTENSION_TRUE to cause only records that the API can validate as secure withe DNSSEC to be returned in the
.I replies_tree
and
.I replies_full lists

.HP 3
dnssec_return_supporting_responses (int)

Set to GETDNS_EXTENSION_TRUE to cause the set of additional DNSSEC-related records needed for validation to be returned in the response object as the list named
.I additional_dnssec
at the top level of the response object

.HP 3
return_both_v4_and_v6 (int)

Set to GETDNS_EXTENSION_TRUE to cause the results of both A and AAAA records for the queried name to be included in the response object.

.HP 3
add_opt_parameters (dict)

TBD (complicated)

.HP 3
add_warning_for_bad_dns

Set to GETDNS_EXTENSION_TRUE to cause each reply in the
.I replies_tree
to contain an additional name whose data type is a list,
.I bad_dns
which contains zero or more ints that indicate the types of bad DNS found in the reply.  
.RS 6
.br
GETDNS_BAD_DNS_CNAME_IN_TARGET: query type does not allow a CNAME pointed to a CNAME
.br
GETDNS_BAD_DNS_ALL_NUMERIC_LABEL: one or more labels is all numeric
.br
GETDNS_BAD_DNS_CNAME_RETURNED_FOR_OTHER_TYPE: query type for other than CNAME returned a CNAME
.RE

.HP 3
specify_class (int)

Set to the DNS class number (other than Internet (IN) class desired in query.

.HP 3
return_api_information (int)

Set to GETDNS_EXTENSION_TRUE to add the following to the top level of the response object:
.RS 6
.br
.I version_string
(bindata) : the version string for this version of the getdns API
.br
.I implementation_string
(bindata) : string set by this library's implementer as a build or version indicator
.br
.I resolver_type
(int) : GETDNS_CONTEXT_RECURSING or GETDNS_CONTEXT_STUB depending on how the context is configured
.br
.I all_context
(dict) : includes names from the context, use with
.I getdns_pretty_print_dict
(3) for debugging
.RE

.HP 3
return_call_debugging (int)

Set to GETDNS_EXTENSION_TRUE to add the name
.I call_debugging
(list) to the top level of the response object that includes a dict for each call made to the API.  TBD: more detail

.LP
This implementation of the getdns API is licensed under the BSD license.

.SH Response Data from Queries

.LP
The callback function contains a pointer to a response object. A response
object is always a dict. The response object always contains at least three
names: replies_full (a list) and replies_tree (a list), and status (an int).
replies_full is a list of DNS replies (each is bindata) as they appear on the
wire. replies_tree is a list of DNS replies (each is a dict) with the various
part of the reply parsed out. status is a status code for the query.

.LP
Because the API might be extended in the future, a response object might also
contain names other than replies_full, replies_tree, and status. Similarly, any
of the dicts described here might be extended in later versions of the API.
Thus, an application using the API must not assume that it knows all possible
names in a dict.

.LP
The following lists the status codes for response objects. Note that, if the
status is that there are no responses for the query, the lists in replies_full
and replies_tree will have zero length.

.HP 3
.B GETDNS_RESPSTATUS_GOOD
At least one response was returned
.HP 3
.B GETDNS_RESPSTATUS_NO_NAME
Queries for the name yielded all negative responses
.HP 3
.B GETDNS_RESPSTATUS_ALL_TIMEOUT
All queries for the name timed out
.HP 3
.B GETDNS_RESPSTATUS_NO_SECURE_ANSWERS
The context setting for getting only secure responses was specified, and at least one DNS response was received, but no DNS response was determined to be secure through DNSSEC.

.LP
The top level of replies_tree can optionally have the following names: canonical_name (a bindata), intermediate_aliases (a list), answer_ipv4_address (a bindata), answer_ipv6_address (a bindata), and answer_type (an int).

.LP
The value of canonical_name is the name that the API used for its lookup. It is
in FQDN presentation format.  The values in the intermediate_aliases list are
domain names from any CNAME or unsynthesized DNAME found when resolving the
original query. The list might have zero entries if there were no CNAMEs in the
path. These may be useful, for example, for name comparisons when following the
rules in RFC 6125.  The value of answer_ipv4_address and answer_ipv6_address
are the addresses of the server from which the answer was received.  The value
of answer_type is the type of name service that generated the response. The
values are:

.RS 3
    GETDNS_NAMETYPE_DNS
    Normal DNS (RFC 1035)
    GETDNS_NAMETYPE_WINS
    The WINS name service (some reference needed)
.RE

.LP
If the call was getdns_address or getdns_address_sync, the top level of
replies_tree has an additional name, just_address_answers (a list). The value
of just_address_answers is a list that contains all of the A and AAAA records
from the answer sections of any of the replies, in the order they appear in the
replies. Each item in the list is a dict with at least two names: address_type
(whose value is a bindata; it is currently either "IPv4" or "IPv6") and
address_data (whose value is a bindata). Note that the
dnssec_return_only_secure extension affects what will appear in the
just_address_answers list. If the DNS returns other
address types, those types will appear in this list as well.

.LP
The API can make service discovery through SRV records easier. If the call was
getdns_service or getdns_service_sync, the top level of replies_tree has an
additional name, srv_addresses (a list). The list is ordered by priority and
weight based on the weighting algorithm in RFC 2782, lowest priority value
first. Each element of the list is dict has at least two names: port and
domain_name. If the API was able to determine the address of the target domain
name (such as from its cache or from the Additional section of responses), the
dict for an element will also contain address_type (whose value is a bindata;
it is currently either "IPv4" or "IPv6") and address_data (whose value is a
bindata). Note that the dnssec_return_only_secure extension affects what will
appear in the srv_addresses list.

.SH Structure of DNS replies_tree

.LP
The names in each entry in the the replies_tree list for DNS responses include
header (a dict), question (a dict), answer (a list), authority (a list), and
additional (a list), corresponding to the sections in the DNS message format.
The answer, authority, and additional lists each contain zero or more dicts,
with each dict in each list representing a resource record.

.LP
The names in the header dict are all the fields from Section 4.1.1. of RFC
1035. They are: id, qr, opcode, aa, tc, rd, ra, z, rcode, qdcount, ancount,
nscount, and arcount. All are ints.

.LP
The names in the question dict are the three fields from Section 4.1.2. of RFC
1035: qname (a bindata), qtype (an int), and qclass (an int).

.LP
Resource records are a bit different than headers and question sections in that
the RDATA portion often has its own structure. The other names in the resource
record dicts are name (a bindata), type (an int), class (an int), ttl (an int)
and rdata (a dict); there is no name equivalent to the RDLENGTH field.

.LP
The rdata dict has different names for each response type. There is a complete
list of the types defined in the API. For names that end in "-obsolete" or
"-unknown", the bindata is the entire RDATA field. For example, the rdata for
an A record has a name ipv4_address (a bindata); the rdata for an SRV record
has the names priority (an int), weight (an int), port (an int), and target (a
bindata).

.LP
Each rdata dict also has a rdata_raw field (a bindata). This is useful for
types not defined in this version of the API. It also might be of value if a
later version of the API allows for additional parsers. Thus, doing a query for
types not known by the API still will return a result: an rdata with just a
rdata_raw.

.LP
It is expected that later extensions to the API will give some DNS types
different names. It is also possible that later extensions will change the
names for some of the DNS types listed above.

.SH FILES
.br /etc/hosts
.br /etc/resolv.conf

.SH EXAMPLES
TBD

.SH DIAGNOSTICS
TBD

.SH "SEE ALSO"
.BR getdns_address (3),
.BR getdns_address_sync (3),
.BR getdns_context (3),
.BR getdns_dict (3),
.BR getdns_general (3),
.BR getdns_general_sync (3),
.BR getdns_hostname (3),
.BR getdns_hostname_sync (3),
.BR getdns_list (3),
.BR getdns_service (3),
.BR getdns_service_sync (3).

.SH REPORTING PROBLEMS
Bug reports should be sent to the getdns-bugs@getdns.net

.SH AUTHORS

The getdns API was documented by Paul Hoffman.  This implementation of the getdns API was written by:
.LP
.RS 3
.br
Neel Goyal, Verisign Inc.
.br
Melinda Shore, No Mountain Software, LLC
.br
Willem Toorop, NLNet Labs
.br
Wouter Wijngaards, NLNet Labs
.br
Glen Wiley, Verisign Inc.
.RE