getdns is an implementation of a modern asynchronous DNS API; the specification was originally edited by Paul Hoffman. It is intended to make all types of DNS information easily available to application developers and non-DNS experts.
Traditional access to DNS data from applications has several limitations:
APIs require applications to have considerable sophistication about DNS data and data types
Some kinds of data about the response (notably, the resource record set time to live) is not exposed via any API, so applications need to process raw protocol responses to get such data
APIs are often blocking, meaning asynchronous access is not possible without some work
Sophisticated uses of the DNS (things like IDNA and DNSSEC validation) require considerable application work, possibly by application developers with little experience with the vagaries of DNS.
getdns also provides an experimental DNS Privacy enabled client called 'stubby' - see below for more details.
The developers are of the opinion that DNSSEC offers a unique global infrastructure for establishing and enhancing cryptographic trust relations. With the development of this API we intend to offer application developers a modern and flexible interface that enables end-to-end trust in the DNS architecture, and which will inspire application developers to implement innovative security solutions in their applications.
Note that this implementation offers additional functionality to supplement that in the official getdns API. Some additions are convenient utility functions but other functionality is experimental prior to be being recommended for inclusion in the official API. The Doxygen documentation provides the details of the full API for this implementation.
This implementation is licensed under the New BSD License (BSD-new).
The project home page at getdnsapi.net provides documentation, binary downloads, and news regarding the getdns API implementation. This README file captures the goals and direction of the project and the current state of the implementation.
If you are just getting started with the library take a look at the section below that describes building and handling external dependencies for the library.
Once it is built you should take a look at
spec/example to see how the library is used.
Download the sources from our github repo or from getdnsapi.net and verify the download using the checksums (SHA1 or MD5) or using gpg to verify the signature. Our keys are available from the pgp keyservers
firstname.lastname@example.org, key id E5F8F8212F77A498
Release numbering follows the Semantic Versioning approach. The code is currently under active development.
The following requirements were met as conditions for the present release:
If you are installing from packages, you have to install the library and also the library-devel (or -dev) for your package management system to get the the necessary compile time files.
External dependencies are linked outside the getdns API build tree (we rely on CMake to find them). We would like to keep the dependency tree short, see Minimising Dependancies for more details.
Required for all builds:
Required for all builds that include recursive functionality:
Required for all builds that include IDN functionality:
Required to build the documentation:
For example, to build on Ubuntu 18.04 or later, you would need the following packages for a full build:
# apt install build-essential libunbound-dev libidn2-dev libssl-dev cmake
If you are building from git, you need to do the following before building:
# git submodule update --init
From release 1.6.0 getdns uses CMake (previous versions used autoconf/libtool). To build from this release and later use:
# cmake . # make
If you are unfamiliar with CMake, see our CMake Quick Start for how to use CMake options to customise the getdns build.
As well as building the getdns library two other tools are installed by default:
Stubby a DNS Privacy enabled client can also be built and installed by using the
BUILD_STUBBY option when running
cmake, see Stubby.
cmake. This removes the dependency on
getdns_convert_alabel_to_ulabel. If you do not need these functions, getdns can be configured to compile without them by setting the
ENABLE_STUB_ONLYis ON, and
USE_LIBIDN2is OFF, getdns has only one dependency left, which is OpenSSL.
Example test queries using
getdns_query (pointed at Google Public DNS) and requesting the
call_reporting extension which provides information on the transport and query time:
getdns_query -s example.com A @188.8.131.52 +return_call_reporting (UDP) getdns_query -s example.com A @184.108.40.206 -T +return_call_reporting (TCP) getdns_query -s example.com A @220.127.116.11 -L +return_call_reporting (TLS without authentication) getdns_query -s getdnsapi.net A +dnssec_return_status +return_call_reporting (DNSSEC)
A project to allow user selection of either OpenSSL or GnuTLS is currently a work in progress. At present a user may select to use GnuTLS for the majority of the supported functionality, however, OpenSSL is still required for some cryptographic functions.
A suite of regression tests are included with the library, if you make changes or just want to sanity check things on your system take a look at src/test. You will need to install libcheck. The check library is also available from many of the package repositories for the more popular operating systems. Note: The tests currently do not run on Windows because of a dependancy on bash.
For the library to be DNSSEC capable, it needs to know the root trust anchor.
The library will try to load the root trust anchor from
/etc/unbound/getdns-root.key by default. This file is expected to have one
DNSKEY resource records in presentation (i.e. zone file)
format. Note that this is different than the format of BIND.keys.
When the root trust anchor is not installed in the default location and a DNSSEC query is done, getdns will try to use the trust anchors published here: http://data.iana.org/root-anchors/root-anchors.xml .
It will validate these anchors with the ICANN Certificate Authority certificate following the procedure described in [RFC7958].
root-anchors.p7s S/MIME signature will be cached in the
$HOME/.getdns directory on Unixes, and the
%appdata%\getdns directory on Windows.
When using trust-anchors from the
root-anchors.xml file, getdns will track the keys in the root DNSKEY rrset and store a copy in
$HOME/.getdns/root.key on Unixes, and
%appdata%\getdns\root.key on Windows.
Only when the KSK DNSKEY's change, a new version of
root-anchors.xml is tried to be retrieved from data.iana.org.
A installed trust-anchor from the default location (
/etc/unbound/getdns-root.key) that fails to validate the root DNSKEY RRset, will also trigger the "Zero configuration DNSSEC" procedure described above.
We have a getdns users list for this implementation.
Tickets and bug reports should be reported via the GitHub issues list.
The goals of this implementation of the getdns API are:
Non-goals (things we will not be doing at least initially) include:
In parallel, the team is actively developing bindings for various languages. For more information, visit this webpage.
The following API calls are documented in getDNS but not supported by the implementation at this time:
The following minor implementation omissions are noted:
Recursive mode does not support:
Stub mode does not support:
The platforms listed here are intended to help ensure that we catch platform specific breakage prior to release.
If you are using FreeBSD 10 getdns can be intalled via 'pkg install getdns'.
getdns should also work on Ubuntu 16.04, however if you require IDN functionality you will have to install a recent version of libidn2 via a ppa e.g. from https://launchpad.net/~ondrej/+archive/ubuntu/php
You will also have to build Unbound from source code to provide libunbound at version >= 1.5.9.
A self-compiled version of OpenSSL or the version installed via Homebrew is required and the options OPENSSL_ROOT_DIR, OPENSSL_CRYPTO_LIBRARY and OPENSSL_SSL_LIBRARY can be used to specify the location of the libraries. Note: If using a self-compiled version, manual configuration of certificates into /usr/local/etc/openssl/certs is required for TLS authentication to work.
If you're using Homebrew, you may run
brew install getdns. By default, this will only build the core library without any 3rd party event loop support.
To install the event loop integration libraries that enable support for libevent, libuv, and libev, run:
brew install getdns --with-libevent --with-libuv --with-libev. All switches are optional.
Note that in order to compile the examples, the
--with-libevent switch is required.
Additionally, getdns is linked against the the OpenSSL library installed by Homebrew. Note that the Homebrew OpenSSL installation clones the Keychain certificates to the default OpenSSL location so TLS certificate authentication should work out of the box.
You will need CMake for Windows. Installers can be downloaded from https://cmake.org/download/.
Windows versions of the following libraries are available using the vcpkg package manager.
Once these are installed, set CMake variables CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH to the vcpkg include and library directories e.g.
To generate a project suitable for use in Visual Studio, select the appropriate Visual Studio generator in CMake. Once generated, the cmake-gui Open Project button can be used to load the project into Visual Studio.
Full support for Windows is a work in progress. The following limitations will be addresses in future:
At present, no native Windows DLL version of libunbound exists; support for linking against libunbound is not currently available. The default build option for ENABLE_STUBONLY is ON for Windows.
The getdns unit tests (built with
make test) require libcheck which is not currently available for Windows and so cannot be built.
The getdns tpkg test suite is not currently supported on Windows.
The detection of the location of the
/etc/hosts file should be optimised - it currently assumes Windows is installed in the default directory on the C: drive
The development team explicitly acknowledges Paul Hoffman for his initiative and efforts to develop a consensus based DNS API. We would like to thank the participants of the getdns-api mailing list (discontinued) for their contributions.