PowerDNS: Difference between revisions
imported>Aerique Update for PowerDNS DNSdist 1.9.10. |
imported>PhotographyEdits use svg logo |
||
| Line 2: | Line 2: | ||
{{distinguish|text=[[pdnsd]], a caching DNS proxy}} | {{distinguish|text=[[pdnsd]], a caching DNS proxy}} | ||
{{Infobox software | {{Infobox software | ||
| name = PowerDNS | | name = PowerDNS | ||
| logo = | | logo = Logo of PowerDNS.svg | ||
| screenshot = | | screenshot = | ||
| caption = | | caption = | ||
| Line 9: | Line 9: | ||
| developer = PowerDNS Community, Bert Hubert | | developer = PowerDNS Community, Bert Hubert | ||
| released = | | released = | ||
| latest release version = | | latest release version = | ||
| latest release date = | | latest release date = | ||
| latest preview version = | | latest preview version = | ||
| latest preview date = | | latest preview date = | ||
| Line 59: | Line 21: | ||
}} | }} | ||
'''PowerDNS''' is a [[Name server|DNS | '''PowerDNS''' is a software project providing a [[Name server|DNS]] authoritative server, recursor and proxy. It is written in [[C++]] and licensed under the [[GNU General Public License|GPL]]. It runs on most [[Unix]] derivatives. PowerDNS features a large number of different ''backends'' ranging from simple [[BIND]] style zonefiles to [[relational database]]s<ref name = "Jeannerot, Azylis Net, 2016" >{{ Cite web | url = http://technique.azylis.net/powerdns/ | title = {{sic|POWERDNS|nolink=y}} | access-date = 27 July 2019 | first = Christophe | last = Jeannerot | date = 21 October 2016 | website = Azylis dot net | language = fr | quote = Nous allons utiliser POWERDNS avec un stockage des tables DNS dans une base de données MARIADB. | archive-url = https://web.archive.org/web/20190727161551/http://technique.azylis.net/powerdns/ | archive-date = 27 July 2019 | df = dmy-all }}</ref> and [[Load balancing (computing)|load balancing]]/[[failover]] [[algorithms]]. | ||
== History == | == History == | ||
| Line 79: | Line 41: | ||
|quote = "PowerDNS was launched in 1999"; "Originally closed source"; "In 2002, all PowerDNS software was released as open source" }}</ref> | |quote = "PowerDNS was launched in 1999"; "Originally closed source"; "In 2002, all PowerDNS software was released as open source" }}</ref> | ||
== | == Components == | ||
PowerDNS [[Name server#Authoritative name server|Authoritative Server]] ( | |||
=== Authoritative server === | |||
PowerDNS [[Name server#Authoritative name server|Authoritative Server]] (pdns_server) consists of a general purpose authoritative server, and multiple [[library (computer science)|dynamically loadable]] [[Front and back ends|backend]]s that both run [[multi-threaded]]. The core handles all packet processing and DNS intelligence, while one or more backends deliver [[DNS record]]s using arbitrary [[computer storage|storage methods]]. | |||
[[DNS zone transfer|Zone transfers]] and update notifications are supported, and the processes can run ''unprivileged'' and ''[[chroot]]ed''. Various ''[[DNS cache|caches]]'' are maintained to speed up query processing. ''[[Run time (program lifecycle phase)|Run-time]] control'' is available through the | [[DNS zone transfer|Zone transfers]] and update notifications are supported, and the processes can run ''unprivileged'' and ''[[chroot]]ed''. Various ''[[DNS cache|caches]]'' are maintained to speed up query processing. ''[[Run time (program lifecycle phase)|Run-time]] control'' is available through the pdns_control command, which allows reloading of separate zones, cache purges, zone notifications and dumps [[statistics]] in [[Multi Router Traffic Grapher]] / [[rrdtool]] format. Realtime information can also be obtained through the optional built-in [[web server]]. | ||
There are many independent projects to create management interfaces for PowerDNS. | There are many independent projects to create management interfaces for PowerDNS. | ||
The PowerDNS [[Name server#Authoritative name server|Authoritative Server]] supports [[DNSSEC]] as of version 3.0. While pre-signed zones can be served, it is also possible to perform online signing & key management. This has the upside of being relatively easy, but the downside that the cryptographic keying material is present on the servers itself (which is also true of any HTTPS server when not used with a [[Hardware security module|HSM]] for example). | The PowerDNS [[Name server#Authoritative name server|Authoritative Server]] supports [[DNSSEC]] as of version 3.0. While pre-signed zones can be served, it is also possible to perform online signing & key management. This has the upside of being relatively easy, but the downside that the cryptographic keying material is present on the servers itself (which is also true of any HTTPS server when not used with a [[Hardware security module|HSM]] for example). | ||
== Recursor == | === Recursor === | ||
PowerDNS Recursor ( | PowerDNS Recursor (pdns_recursor<ref>{{cite web|url=https://doc.powerdns.com/recursor/ |title=PowerDNS Recursor |publisher=Doc.powerdns.com |date= |accessdate=2014-05-11}}</ref>) is a ''resolving'' DNS server, that runs as a separate process. | ||
This part of PowerDNS uses a combination of native threads and user-space threads, through the use of [[Boost (C++ libraries)|Boost]] and the MTasker library,<ref>[http://ds9a.nl/mtasker/ MTasker<!-- Bot generated title -->]</ref> which is a simple cooperative multitasking library. It is also available as a standalone package. | This part of PowerDNS uses a combination of native threads and user-space threads, through the use of [[Boost (C++ libraries)|Boost]] and the MTasker library,<ref>[http://ds9a.nl/mtasker/ MTasker<!-- Bot generated title -->]</ref> which is a simple cooperative multitasking library. It is also available as a standalone package. | ||
| Line 96: | Line 59: | ||
It does not have to run a pdns_server process as a gatekeeper for pdns_recursor, if the goal is simply to provide caching/recursing/resolving nameservice as running pdns_recursor on its own is even more efficient than behind the authoritative component. | It does not have to run a pdns_server process as a gatekeeper for pdns_recursor, if the goal is simply to provide caching/recursing/resolving nameservice as running pdns_recursor on its own is even more efficient than behind the authoritative component. | ||
Support for [[DNSSEC]] validation was added to the | Support for [[DNSSEC]] validation was added to the pdns_recursor in version 4.0. | ||
== DNSdist == | === DNSdist === | ||
PowerDNS DNSdist ( | PowerDNS DNSdist (dnsdist<ref>{{cite web|url=https://dnsdist.org/ |title=PowerDNS DNSdist |publisher=dnsdist.org |date= |accessdate=2023-05-11}}</ref>) is a caching DNS proxy, with many features including: | ||
* Load Balancing of DNS Queries | * Load Balancing of DNS Queries | ||
Latest revision as of 16:32, 24 June 2025
Template:Short description Script error: No such module "Distinguish". Script error: No such module "Infobox".Template:Template otherScript error: No such module "Check for unknown parameters".Template:Main other
PowerDNS is a software project providing a DNS authoritative server, recursor and proxy. It is written in C++ and licensed under the GPL. It runs on most Unix derivatives. PowerDNS features a large number of different backends ranging from simple BIND style zonefiles to relational databases[1] and load balancing/failover algorithms.
History
PowerDNS development began in 1999 and was originally a commercial proprietary product. In November 2002, the source code was made public under the open-source GPL v2 license.[2][3]
Components
Authoritative server
PowerDNS Authoritative Server (pdns_server) consists of a general purpose authoritative server, and multiple dynamically loadable backends that both run multi-threaded. The core handles all packet processing and DNS intelligence, while one or more backends deliver DNS records using arbitrary storage methods.
Zone transfers and update notifications are supported, and the processes can run unprivileged and chrooted. Various caches are maintained to speed up query processing. Run-time control is available through the pdns_control command, which allows reloading of separate zones, cache purges, zone notifications and dumps statistics in Multi Router Traffic Grapher / rrdtool format. Realtime information can also be obtained through the optional built-in web server.
There are many independent projects to create management interfaces for PowerDNS.
The PowerDNS Authoritative Server supports DNSSEC as of version 3.0. While pre-signed zones can be served, it is also possible to perform online signing & key management. This has the upside of being relatively easy, but the downside that the cryptographic keying material is present on the servers itself (which is also true of any HTTPS server when not used with a HSM for example).
Recursor
PowerDNS Recursor (pdns_recursor[4]) is a resolving DNS server, that runs as a separate process.
This part of PowerDNS uses a combination of native threads and user-space threads, through the use of Boost and the MTasker library,[5] which is a simple cooperative multitasking library. It is also available as a standalone package.
It does not have to run a pdns_server process as a gatekeeper for pdns_recursor, if the goal is simply to provide caching/recursing/resolving nameservice as running pdns_recursor on its own is even more efficient than behind the authoritative component.
Support for DNSSEC validation was added to the pdns_recursor in version 4.0.
DNSdist
PowerDNS DNSdist (dnsdist[6]) is a caching DNS proxy, with many features including:
- Load Balancing of DNS Queries
- DNS Encryption Support - DNS over HTTPS, DNS over TLS, both upstream and downstream (i.e. to clients and backends)
- Lua Policy Engine - Extensive capabilities for creating rules for processing DNS packets, such as changing the response, re-routing a query or blocking traffic over a max QPS from a subnet.
- Dynamic Rule Generation - Used to create Dynamic Blocks which are short-lived rules, automatically inserted based on configurable thresholds and the analysis of recently received traffic. Used to deal with DoS attacks
DNSdist is available as a standalone package, and can be deployed with PowerDNS Authoritative Server or Recursor, or any other third-party DNS server.
See also
Script error: No such module "Portal".