Unbound: A Validating, Recursive DNS Resolver
Unbound is a validating, recursive, and caching DNS resolver from NLnet Labs, written in C and released under the BSD-3-Clause license with 4,776 GitHub stars. It's software you compile and run yourself, configured through the unbound.conf(5) man page rather than a dashboard. Reach for it if you want full control and don't mind building from source; skip it if a C toolchain and a conf file feel like more than you need for recursive DNS.
What is Unbound?
Unbound is a DNS resolver that performs recursive lookups, validates DNSSEC, and caches responses inside a single standalone process built in C by NLnet Labs. The README calls it a lean, speed-focused build that stays current with open standards, and it ships as source you compile with ./configure && make && make install rather than a packaged app or web dashboard.
Key Capabilities of Unbound
- โCombines recursive lookup, DNSSEC validation, and response caching in one resolver process, per the repository's own description.
- โWritten entirely in C and distributed under the permissive BSD-3-Clause license.
- โConfigured through the unbound.conf(5) man page, which is installed alongside the binary and also published on the docs site.
- โShips an example configuration file, doc/example.conf, with minimal inline documentation as a starting template.
- โSupports optional libevent integration via the --with-libevent configure flag, useful when a deployment needs many outgoing ports at once โ the README's own example is 10000.
- โFalls back to a builtin event-handling alternative when libevent isn't used, capped at 256 outgoing ports but described in the README as just as capable and a touch quicker.
- โTagged on GitHub with dns-privacy and dnssec topics alongside recursor and resolver.
- โMaintained by NLnet Labs, with a public GitHub issue tracker and a community forum for feedback.
Advantages of Using Unbound
- โNo hosted-service lock-in โ Unbound is resolver software you build and run yourself under a permissive BSD-3-Clause license.
- โConfiguration is documented through an actual man page, unbound.conf(5), not just prose scattered in a README.
- โThe libevent decision is spelled out plainly in the README: skip it for a slightly faster builtin path, or add it for high outgoing-port counts.
- โDNSSEC validation and DNS privacy are prominent enough to be listed as repository topics rather than buried features.
- โA public issue tracker and a community forum both exist specifically for user feedback, per the README.
Considerations for Unbound Deployment
- โณThe README excerpt available doesn't walk through DNSSEC or DNS-privacy configuration step by step; both are listed topics but not explained inline.
- โณBuilding straight from the repository adds flex and bison to the dependency list on top of the C toolchain, OpenSSL, and libexpat.
- โณNo version number, release cadence, or changelog appears in the README text, so freshness isn't something you can judge from it alone.
- โณThere's no GUI or managed-hosting option described anywhere โ deployment means compiling and operating the binary yourself.
- โณThe builtin outgoing-port handling tops out at 256 ports at once; anything beyond that requires opting into libevent.
Getting Started: Compiling Unbound
Unbound is built from source. The README lists the prerequisites as a C toolchain, OpenSSL with its include files, and libexpat; building straight from the repository (rather than a release tarball) additionally requires flex and bison. With those in place, the whole build is three commands: ./configure && make && make install. libevent is optional โ add --with-libevent to the configure step if you want it, mainly for setups juggling many outgoing ports; without it, Unbound falls back to a builtin alternative capped at 256 ports at once.
Unbound Alternatives
Unbound FAQs
Unbound is released under the BSD-3-Clause license, as listed on its GitHub repository.
Unbound is described on GitHub as a validating DNS resolver, and dnssec is one of its listed repository topics, though the README excerpt here doesn't detail the validation configuration steps.
DNS privacy is one of Unbound's own repository topics on GitHub, alongside dnssec and recursor, though the specific privacy configuration isn't spelled out in the README text provided.
Unbound is written in C, per its GitHub repository metadata.
An example configuration with minimal inline documentation ships in the repository at doc/example.conf, and the full option reference is the unbound.conf(5) man page, also published on the Unbound docs site.
No. libevent is optional and enabled with --with-libevent at configure time; without it, Unbound uses a builtin alternative the README calls just as capable and a touch quicker, though capped at 256 outgoing ports at once.
The problem it solves
Recursive DNS lookups usually go one of two ways: outsourced to whichever public resolver your OS or ISP picked, or handled by a general-purpose DNS server bundled with far more than resolver duties. Unbound's README frames its own reason for existing around neither of those โ it's built to be, in its own words, fast and lean, with DNSSEC validation and caching done locally by a piece of software whose only job is resolving and validating queries, not also serving zones or running DHCP.
Best use cases
- โขRunning your own validating, recursive resolver on a server instead of forwarding every client query to a third-party public resolver.
- โขEnabling --with-libevent when a deployment needs thousands of concurrent outgoing queries, matching the README's own 10000-port example.
- โขTesting or auditing DNSSEC validation behavior in a resolver you compile and control end to end.
- โขStarting a production unbound.conf from the shipped doc/example.conf template rather than writing configuration from scratch.
Who should try it โ and who should skip
Try Unbound if you're comfortable compiling C software from source and want a DNS resolver you fully control: write your own unbound.conf, decide whether libevent earns its keep for your outgoing-port count, and validate DNSSEC locally instead of trusting someone else's resolver. Skip it if you want DNS handled without a toolchain and a man page, or if you need DHCP bundled in too โ Unbound only resolves and validates, and its README points everything past compiling straight at the external docs site.
Related repositories
Is unbound worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of unbound.
