Comparison of DNS server software

This article presents a comparison of the features, platform support, and packaging of many independent implementations of Domain Name System (DNS) name server software.

Servers compared


Each of these DNS servers is an independent implementation of the DNS protocols, capable of resolving DNS names for other computers, publishing the DNS names of computers, or both. Excluded from consideration are single-feature DNS tools (such as proxies, filters, and firewalls) and redistributions of servers listed here (many products repackage BIND, for instance, with proprietary user interfaces).

DNS servers are grouped into several categories of specialization of servicing domain name system queries. The two principal roles, which may be implemented either uniquely or combined in a given product are:

  • Authoritative server: authoritative name servers publish DNS mappings for domains under their authoritative control. Typically, a company (e.g. "Acme Example Widgets") would provide its own authority services to respond to address queries, or for other DNS information, for These servers are listed as being at the top of the authority chain for their respective domains, and are capable of providing a definitive answer. Authoritative name servers can be primary name servers, also known as master servers, i.e. they contain the original set of data, or they can be secondary or slave name servers, containing data copies usually obtained from synchronization directly with the primary server, either via a DNS mechanism, or by other data store synchronization mechanisms.
  • Recursive server: recursive servers (sometimes called "DNS caches", "caching-only name servers") provide DNS name resolution for applications, by relaying the requests of the client application to the chain of authoritative name servers to fully resolve a network name. They also (typically) cache the result to answer potential future queries within a certain expiration (time-to-live) period. Most Internet users access a recursive server provided by their internet service provider to locate internet hosts such as



F5 Networks BIG-IP product line offers DNS as an authoritative or recursive server and adds additional security measures. Key advantage is to use the same application delivery controller to support DNS and application acceleration.[citation needed]

BIND is the de facto standard DNS server. It is a free software product and is distributed with most Unix and Linux platforms, where it is most often also referred to as named (name daemon). It is the most widely deployed DNS server.[1] Historically, BIND underwent three major revisions, each with significantly different architectures: BIND4, BIND8, and BIND9. BIND4 and BIND8 are now technically obsolete and not considered in this article. BIND9 is a ground-up rewrite of BIND featuring complete DNSSEC support in addition to other features and enhancements.

Internet Systems Consortium started development of a new version, BIND 10. Its first release was in April 2010, but ISC involvement concluded with the release of BIND 10 version 1.2 in April 2014. ISC cited a lack of resources to continue development of BIND 10, and they reaffirmed their commitment to BIND9.[2]

The BIND 10 codebase continues on as an open source project. It is not included in this comparison at this time.

CNR includes a commercial DNS server from Cisco Systems usually used in conjunction with the CNR DHCP (Dynamic Host Configuration Protocol) server. It supports high rates of dynamic update.

CoreDNS is the recommended DNS server[3] for Kubernetes and graduated from the CNCF in 2019.[4]

Dnsmasq is a lightweight, easy to configure DNS forwarder, designed to provide DNS (and optionally DHCP and TFTP) services to a small-scale network. It can serve the names of local machines which are not in the global DNS.

Dnsmasq accepts DNS queries and either answers them from a small, local cache or forwards them to a real, recursive DNS server. It loads the contents of /etc/hosts, so that local host names which do not appear in the global DNS can be resolved.

Djbdns is a collection of DNS applications, including tinydns, which was the second most used free software DNS server in 2004.[1] It was designed by Daniel J. Bernstein, author of qmail, with an emphasis on security considerations. In March 2009, Bernstein paid $1000 to the first person finding a security hole in djbdns.[5] The source code is not centrally maintained and was released into the public domain in 2007. There are multiple forks and more than a dozen patches to add additional features to djbdns.

gdnsd is a DNS server designed for geographic balancing.[6] gdnsd is the DNS server used by Wikipedia for its servers and networking.[7]

Knot DNS is a free software authoritative DNS server by CZ.NIC. Knot DNS aims to be a fast, resilient DNS server usable for infrastructure (root and TLD) and DNS hosting services. Knot DNS supports DNSSEC signing and among others hosts root zone (B, K, and L root name servers), several top-level domains.

Knot Resolver


Knot Resolver is an open source modern resolver implementation designed for scalability, resiliency, and flexibility. Its core architecture is tiny and efficient, and most of the rich features are implemented as optional modules, which limits attack surface and improves performance. Many resolver features are available out-of-the-box as modules while keeping core tiny and efficient. Modular architecture provides a state-machine like API for extensions, such as C and Lua modules.[8]

MaraDNS is a free software DNS server by Sam Trenholme that claims a good security history and ease of use.[9] [10] In order to change any DNS records, MaraDNS needs to be restarted. Like djbdns dnscache, the MaraDNS 2.0 stand-alone recursive resolver ("Deadwood") does not use threads.[11]

Windows DNS Server [12] component of Microsoft DNS. The same software can be configured to support authoritative, recursive and hybrid mode. The software is integrated with Active Directory which makes it the default DNS software for many enterprise networks that are based on Active Directory. It also allows creating zones by the standard DNS zone file. The software comes packaged as a role in Windows Server. The server software is shipped with a command line application dnscmd,[13] a DNS management GUI wizard, and a DNS PowerShell[14] package. In Windows Server 2012, the Windows DNS added support for DNSSEC,[15] with full-fledged online signing, with Dynamic DNS and NSEC3 support, along with RSASHA and ECDSA signing algorithms. It provides an inbuilt key storage provider and support for any third party CNG compliant key storage provider. User interface and PowerShell support for managing DNS and DNSSEC were improved as well. In the Windows Server 2016, the DNS Server supports DNS policies using which the admins can have more control over the name resolution process.[16]

NSD is a free software authoritative server provided by NLNet Labs. NSD is a test-bed server for DNSSEC; new DNSSEC protocol features are often prototyped using the NSD code base. NSD hosts several top-level domains, and operates three of the root nameservers.

Pdnsd is a caching DNS proxy server that stores cached DNS records on disk for long term retention. Pdnsd is designed to be highly adaptable to situations where net connectivity is slow, unreliable, unavailable, or highly dynamic, with limited capability of acting as an authoritative nameserver. It is licensed under the GPL.[17]

Posadis is a free software DNS server, written in C++, featuring Dynamic DNS update support.

PowerDNS is a free software DNS server with a variety of data storage back-ends and load balancing features. Authoritative and recursive server functions are implemented as separate applications, as well as a separate DNS caching proxy (dnsdist) which implements features such as DNS over HTTPS.

DNS Authority is commercial authoritative name server software from Secure64, the company that built Genuinely Secure DNS applications and operating system and completely automated the deployment of DNSSEC.

DNS Cache is scalable, highly secure recursive DNS software from Secure64 which provides built-in protection against high-volume denial of service attacks, including Pseudo Random Sub Domain (PRSD) attacks.

Simple DNS Plus is a commercial DNS server product that runs under Microsoft Windows with an emphasis on a simple-to-use GUI. Maintenance of the software appears to have slackened in recent years.

Technitium DNS Server [18][19] is a free, opensource [20] (GPLv3),[21] cross platform, authoritative, caching and recursive DNS server software. It supports DNS-over-TLS, DNS-over-HTTPS, and DNS-over-QUIC encrypted DNS protocols.[22] It also supports DNSSEC signing and validation for RSA and ECDSA algorithms with both NSEC and NSEC3.

The DNS server also features blocking domain names using block lists [23] and also supports using HTTP or SOCKS5, for transport of DNS requests over Tor network.[24]

The DNS server supports running independently developed plugins that can be used to process and respond to DNS requests. It also provides a HTTP API that can be used by 3rd party software to manage the DNS server.[25]

Unbound is a validating, recursive and caching DNS server designed for high performance. It was released on May 20, 2008 (version 1.0.0) as free software licensed under the BSD license by NLnet Labs. It is installed as part of the base system in FreeBSD starting with version 10.0, and in NetBSD with version 8.0. A version is also available in OpenBSD version 5.6 and beyond. (Previous versions of FreeBSD shipped with BIND.)

YADIFA is a BSD-licensed, memory-efficient DNS server written in C. The acronym YADIFA stands for Yet Another DNS Implementation For All. It was created by EURid, which operates the .eu top-level domain.[26]



Some DNS features are relevant only to recursive servers, or to authoritative servers. As a result, a feature matrix such as the one in this article cannot by itself represent the effectiveness or maturity of a given implementation.

Another important qualifier is the server architecture. Some DNS servers provide support for both server roles in a single, "monolithic" program. Others are divided into smaller programs, each implementing a subsystem of the server. As in the classic Computer Science microkernel debate, the importance and utility of this distinction is hotly debated. The feature matrix in this article does not discuss whether DNS features are provided in a single program or several, so long as those features are provided with the base server package and not with third-party add-on software.

Explanation of features

A major category of DNS server functionality, see above.
A major category of DNS server functionality, see above.
Recursion Access Control
Servers with this feature provide control over which hosts are permitted DNS recursive lookups. This is useful for load balancing and service protection.
Secondary Mode (or Slave Mode)
Authoritative servers can publish content that originates from primary data storage (such as zone files or databases connected to business administration processes)--sometimes also called 'master' servers--or can be secondary (or slave) servers, republishing content fetched from and synchronized with such primary servers. Servers with a "secondary mode" feature have a built-in capability to retrieve and republish content from other servers. This is typically, though not always, provided using the AXFR DNS protocol.
Servers with this feature provide recursive services for applications, and cache the results so that future requests for the same name can be answered quickly, without a full DNS lookup. This is an important performance feature, as it significantly reduces the latency of DNS requests.
Servers with this feature implement some variant of the DNSSEC protocols. They may publish names with resource record signatures (providing a "secure authority service"), and may validate those signatures during recursive lookups (providing a "secure resolver"). DNSSEC is becoming more widespread as the deployment of a DNSSEC root key has been done by ICANN. Deployment to individual sites is growing as top level domains start to deploy DNSSEC too. The presence of DNSSEC features is a notable characteristic of a DNS server.
Servers with this feature typically provide DNSSEC services. In addition, they support the TSIG (Transaction SIGnature) protocol, which allows DNS clients to establish a secure session with the server to publish Dynamic DNS records or to request secure DNS lookups without incurring the cost and complexity of full DNSSEC support.
Servers with this feature are capable of publishing or handling DNS records that refer to IPv6 addresses. In addition to be fully IPv6 capable they must implement IPv6 transport protocol for queries and zone transfers in secondary/primary relationships and forwarder functions.
Servers with this feature can publish information for wildcard records, which provide data about DNS names in DNS zones that are not specifically listed in the zone.
Split horizon
Servers with the split-horizon DNS feature can give different answers depending on the source IP address of the query.

Feature matrix

Server Authoritative Recursive Recursion ACL Secondary mode Caching DNSSEC TSIG IPv6 Wildcard Free Software Interface split horizon DNS over HTTPS DNS over QUIC
BIG-IP DNS Yes Yes Yes Yes Yes Yes Yes Yes Yes No API, command line Yes Yes No
BIND Yes Yes Yes Yes Yes Yes Yes Yes (since 9.x) Yes (since 4.x) Yes Web[Note 1], command line Yes Yes No [Note 2]
PowerDNS Yes Yes Yes Yes[Note 3] Yes Yes (since 3.0) [Note 4] Yes (since 3.0) Yes[Note 3] Yes Yes REST, Web[Note 5], command line Partial[Note 6] Yes (in dnsdist) No [Note 7]
CoreDNS Yes Partial via proxying Yes Yes Yes Yes Yes Yes Yes Yes API Yes Yes No
djbdns Yes Yes Yes Yes[Note 8] Yes Partial[Note 9] No Partial via generic records. [7] Partial[Note 10] Yes command line and web (VegaDNS & NicTool) Yes[Note 11] No No
dbndns Yes Yes Yes Yes Yes No No Yes Partial Yes command line and web Yes No No
pdnsd Partial Yes Partial Partial Yes No [27] Partial Yes Yes Yes command line, pdnsd-ctl program Partial No No
MaraDNS Yes Yes Yes Partial[Note 12] Yes No No Partial Yes Yes command line No No No
Posadis Yes Yes Yes Yes Yes No No Yes Yes Yes command line, API No No No
Unbound Partial Yes Yes Yes Yes No Yes Yes Yes command line, API Yes Yes Partial
Dnsmasq Partial[Note 13] No No No Yes Yes (since 2.69) [Note 14] No Yes Yes Yes command line Partial[Note 15] No
NSD Yes No Yes Yes Yes Yes Yes Yes command line No No
Knot DNS Yes No Yes Yes Yes Yes Yes Yes command line Yes[Note 16] Yes[Note 17]
Knot Resolver No Yes Yes Yes Yes No[Note 18] Yes No Yes cli / socket No[Note 19] Yes No
YADIFA Yes No Yes Yes Yes Yes Yes Yes command line No No No
Microsoft DNS Yes Yes Yes[Note 20] Yes Yes Yes[Note 21] Yes[Note 22] Yes[Note 23] Yes No GUI, command line, API[Note 24], WMI[Note 25], RPC[Note 26] Yes[Note 20] No
Simple DNS Plus Yes Yes Yes Yes Yes Yes Yes Yes Yes No GUI, Web, command line Yes[Note 27] Yes No
Secure64 DNS Authority Yes No No Yes No Yes Yes Yes Yes No Command Line or Web GUI Yes No
Secure64 DNS Cache No Yes Yes No Yes Yes No Yes Yes No Command Line or Web GUI Yes No
Technitium DNS Server Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Web GUI or HTTP API Yes Yes Yes
Server Authoritative Recursive Recursion ACL Secondary mode Caching DNSSEC TSIG IPv6 Wildcard Free Software Interface split horizon DNS over HTTPS DNS over QUIC
  1. ^ A BIND configuration module is available for Webmin in many Linux distributions.
  2. ^ BIND does not support DoQ yet
  3. ^ a b IPv6 primary/secondary support in PowerDNS is incomplete in versions <3.0. Zone transfers in primary/secondary replication over IPv6 is supported since 3.0.
  4. ^ Full DNSSEC support in PowerDNS arrived in version 3.0. In lower versions, it is currently restricted to being able to serve DNSSEC-related RRs.
  5. ^ suggested enhancements at
  6. ^ Use the geoip backend for a split-horizon configuration.
  7. ^ PowerDNS does not support DoQ yet and may only support it in the separate package dnsdist. [1]
  8. ^ djbdns provides facilities to transfer zones; after completing the zone transfer, djbdns can act as an authoritative server for that zone. Consult the axfr-get documentation for further information.
  9. ^ A patch for publishing authoritative DNSSEC-protected data is available at [2].
  10. ^ djbdns supports wildcard DNS records, but not in a way that conforms with the RFCs.
  11. ^ This is not the same as views in bind. But it is a solution with comparable capabilities. See: section of tinydns-data.
  12. ^ MaraDNS cannot directly provide secondary support. Instead, a zone transfer is needed, after which MaraDNS will act as an authoritative server for that zone. See DNS Slave for further information.
  13. ^ dnsmasq has limited authoritative support, intended for internal network use rather than public Internet use.[citation needed] A records are supported via /etc/hosts, and there is some MX, TXT and SRV record support via the command line.
  14. ^ DNSSEC validation was added in Dnsmasq version 2.69 [3]. Earlier versions could only pass through validation results from their own upstream nameservers.[4]
  15. ^ Dnsmasq can do basic split-horizon DNS based on the interface of the source request using the localise-queries configuration parameter.
  16. ^ Knot DNS provides query source address based responses via its geoip and queryacl modules.
  17. ^ Knot DNS Version 3.3.0
  18. ^ As of v5.5.2 This just selects rule based on the key name, it doesn’t verify the key or signature yet. [5]
  19. ^ Setups like split-horizon which depend on isolated DNS caches are explicitly not supported.
  20. ^ a b In Windows Server technical Preview (2016), you can create DNS policies to control how a DNS Server handles DNS queries based on different parameters. This supports Recursion control, location aware responses, split-brain deployment, filters etc. [6] configuration parameter.
  21. ^ Windows Server 2008 R2 supports DNSSEC, however dynamic DNS is not supported for DNSSEC-signed zones. It is fully supported in Windows Server 2012. For earlier versions, including Windows Server 2003, DNSSEC functionality must be manually activated in the registry Archived 2008-03-25 at the Wayback Machine. In these versions, the DNSSEC support is sufficient to act as a slave/secondary server for a signed zone, but not sufficient to create a signed zone (lack of key generation and signing utilities).
  22. ^ Microsoft DNS supports the GSS-TSIG algorithm for Secure Dynamic Update when integrated with Active Directory, using RFC 3645, an application of GSS-API RFC 2743.
  23. ^ IPv6 functionality in the Microsoft DNS server is only available on Windows Server 2003 and newer.
  24. ^ "Microsoft DNS Server API Reference". Retrieved 2011-10-26.
  25. ^ "Microsoft DNS WMI Provider Specification". Retrieved 2011-10-26.
  26. ^ MS-DNSP DNS Server Management Protocol Specification (uses RPCs)
  27. ^ Simple DNS Plus does not have "views" in the same way as BIND, but has a "NAT IP Alias" feature which allows host records to resolve to different IP addresses depending on where the DNS request comes from.



In this overview of operating system support for the discussed DNS server, the following terms indicate the level of support:

  • No indicates that it does not exist or was never released.
  • Partial indicates that while it works, the server lacks important functionality compared to versions for other OSs; it is still being developed however.
  • Beta indicates that while a version is fully functional and has been released, it is still in development (e.g. for stability).
  • Yes indicates that it has been officially released in a fully functional, stable version.
  • Included indicates that the server comes pre-packaged with or has been integrated into the operating system.

This compilation is not exhaustive, but rather reflects the most common platforms today.

Server BSD Solaris Linux Mac OS X Windows
BIND Yes Yes Yes Yes Partial[Note 1][Note 2]
Microsoft DNS No No No No Included[Note 3]
djbdns Yes Yes Yes Yes No
Dnsmasq Yes Yes Yes Yes No
Simple DNS Plus No No No No Yes
NSD Yes Yes Yes Yes No
Knot DNS Yes No Yes Yes No
Knot Resolver Yes ? Yes Yes ?
PowerDNS Yes Yes [8] Yes Beta No
MaraDNS Yes Yes [9] Yes Yes Partial
pdnsd Yes Partial[28] Yes Yes No
Posadis Yes Yes Yes Yes Yes [10]
Unbound Yes Yes Yes Yes Yes
Cisco Network Registrar No Yes Yes No Yes
YADIFA Yes Yes Yes Yes No
Secure64 DNS Authority No No Yes No No
Secure64 DNS Cache No No Yes No No
Technitium DNS Server No No Yes Yes Yes
  1. ^ BIND is available for Windows NT-based systems by ftp (including Windows 2000, XP, and Server 2003) in a port (in contrib directory) known as ntbind (from version 9.3.3 Windows builds are present).
  2. ^ Support for compiling and running BIND 9 natively on Windows has been completely removed as of 9.18.0.
  3. ^ The functionality available with the Microsoft DNS server varies depending on the version of the underlying operating system; such as most Windows Server components, it is upgraded only with the rest of the operating system. Certain functionality, such as DNSSEC and IPv6 support, is only available in the Windows Server 2000-2003 version. Windows 2000 Server includes TSIG support. The Microsoft DNS Server is not available on Windows client operating systems such as Windows XP.


Server Creator Cost (USD) Public source code Software license
BIND Internet Systems Consortium Free Yes BSD, MPL 2.0 for 9.11+
Microsoft DNS Microsoft Included with Windows Server No Clickwrap license
djbdns Daniel J. Bernstein Free Yes Public domain
Dnsmasq Simon Kelley Free Yes GPL
Simple DNS Plus JH Software $79 – $379 No Clickwrap license
NSD NLnet Labs Free Yes BSD variant
Knot DNS CZ.NIC Free Yes GPL
Knot Resolver CZ.NIC Free Yes GPL
PowerDNS PowerDNS.COM BV / Bert Hubert Free Yes GPL
MaraDNS Sam Trenholme Free Yes BSD variant
pdnsd Thomas Moestl and Paul Rombouts Free Yes GPL
Posadis Meilof Veeningen Free Yes GPL
Unbound NLnet Labs Free Yes BSD
Secure64 DNS Authority Secure64 Unpublished price No Clickwrap license
Secure64 DNS Cache Secure64 Unpublished price No Clickwrap license
Technitium DNS Server Technitium Free Yes GPL

See also



  1. ^ a b Moore, Don (2004). "DNS server survey". Retrieved 2005-01-06.
  2. ^ "ISC Concludes BIND 10 Development with Release 1.2". 17 April 2014.
  3. ^ "Customizing DNS Service".
  4. ^ Claburn, Thomas (2019-01-24). "CoreDNS is all grown up now and ready to roll: Kubernetes network toolkit graduates at last". The Register. Retrieved 2020-01-20.
  5. ^ "The djbdns prize claimed". Archived from the original on 2009-03-05. Retrieved 2009-03-04.
  6. ^ "gdnsd". Retrieved 2022-09-23.
  7. ^ "DNS - Wikitech". Retrieved 2022-09-23.
  8. ^ "Knot Resolver". Knot Resolver. Retrieved 11 January 2024.
  9. ^ Mens, Jan-Piet (2008). Alternative DNS Servers: Choice and Deployment, and Optional SQL/LDAP Back-Ends (Paperback). UIT Cambridge Ltd. ISBN 978-0-9544529-9-5.
  10. ^ Danchev, Dancho. "How OpenDNS, PowerDNS and MaraDNS remained unaffected by the DNS cache poisoning vulnerability". ZDNet. Retrieved 2009-10-10.
  11. ^ "MaraDNS - A security-aware DNS server". MaraDNS. Retrieved 2010-12-15.
  12. ^ "Developer tools, technical documentation and coding examples". Microsoft.
  13. ^ "DNSCMD Syntax: Domain Name System(DNS)". 3 September 2012.
  14. ^ "Domain Name System (DNS) Server Cmdlets". Archived from the original on 2015-05-18. Retrieved 2015-05-08.
  15. ^ "DNSSEC in Windows Server 2012". 31 August 2016.
  16. ^ "What's New in DNS Server in Windows Server 2016". 20 October 2021.
  17. ^ "The pdnsd Homepage". Retrieved 2011-10-26.
  18. ^ "Technitium DNS Server".
  19. ^ "DNS Server (and Related) Software for Unix".
  20. ^ "Source Code". GitHub.
  21. ^ "GPLv3 License". GitHub.
  22. ^ "DNS Privacy Implementation Status".
  23. ^ "5 Top Self-Hosted Opensource DNS Servers Like Pi-Hole". 8 April 2023.
  24. ^ "Configuring DNS Server For Privacy & Security".
  25. ^ "Technitium DNS Server API Documentation". GitHub.
  26. ^ "About YADIFA". Retrieved 2013-04-11.
  27. ^ "pdns NEWS". Archived from the original on 2013-06-25. Retrieved 2013-03-29. "no support for the DNSSEC protocol itself yet in pdnsd"
  28. ^ "pdnsd homepage". Retrieved 2013-03-29. "pdnsd was started on Linux, and has since been ported to FreeBSD (and Cygwin and Darwin). 90% of the source code should be easily portable to POSIX- and BSD-compatible systems, provided that those systems support the POSIX threads (pthreads). The rest might need OS-specific rewrites."