Previous topic

Security of the PowerDNS Recursor

Next topic

Manual Pages

This Page

PowerDNS Recursor Settings

Each setting can appear on the command line, prefixed by ‘–’, or in the configuration file. The command line overrides the configuration file.

Note: Settings marked as ‘Boolean’ can either be set to an empty value, which means on, or to ‘no’ or ‘off’ which means off. Anything else means on.

As an example:

  • serve-rfc1918 on its own means: do serve those zones.
  • serve-rfc1918=off or serve-rfc1918=no means: do not serve those zones.
  • Anything else means: do serve those zones.

aaaa-additional-processing

  • Boolean
  • Default: No

If turned on, the recursor will attempt to add AAAA IPv6 records to questions for MX records and NS records. Can be quite slow as absence of these records in earlier answers does not guarantee their non-existence. Can double the amount of queries needed.

allow-from

  • IP ranges, separated by commas
  • Default: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16

Netmasks (both IPv4 and IPv6) that are allowed to use the server. The default allows access only from RFC 1918 private IP addresses. Due to the aggressive nature of the internet these days, it is highly recommended to not open up the recursor for the entire internet. Questions from IP addresses not listed here are ignored and do not get an answer.

allow-from-file

  • Path

Like allow-from, except reading from file. Overrides the allow-from setting. To use this feature, supply one netmask per line, with optional comments preceded by a “#”.

any-to-tcp

  • Boolean
  • Default: no

Answer questions for the ANY type on UDP with a truncated packet that refers the remote server to TCP. Useful for mitigating ANY reflection attacks.

api-config-dir

New in version 4.0.0.

  • Path
  • Default: unset

Directory where the REST API stores its configuration and zones.

api-key

New in version 4.0.0.

  • String
  • Default: unset

Static pre-shared authentication key for access to the REST API.

api-readonly

Changed in version 4.2.0: This setting has been removed.

  • Boolean
  • Default: no

Disallow data modification through the REST API when set.

api-logfile

Changed in version 4.2.0: This setting has been removed.

  • Path
  • Default: unset

Location of the server logfile (used by the REST API).

auth-can-lower-ttl

  • Boolean
  • Default: no

Authoritative zones can transmit a TTL value that is lower than that specified in the parent zone. This is called a ‘delegation inconsistency’. To follow RFC 2181 section 5.2 and 5.4 to the letter, enable this feature. This will mean a slight deterioration of performance, and it will not solve any problems, but does make the recursor more standards compliant. Not recommended unless you have to tick an ‘RFC 2181 compliant’ box.

auth-zones

  • Comma separated list of ‘zonename=filename’ pairs

Zones read from these files (in BIND format) are served authoritatively. DNSSEC is not supported. Example:

auth-zones=example.org=/var/zones/example.org, powerdns.com=/var/zones/powerdns.com

carbon-interval

  • Integer
  • Default: 30

If sending carbon updates, this is the interval between them in seconds. See Metrics and Statistics.

carbon-ourname

  • String

If sending carbon updates, if set, this will override our hostname. Be careful not to include any dots in this setting, unless you know what you are doing. See Sending metrics to Graphite/Metronome over Carbon.

carbon-server

  • IP address

If set to an IP or IPv6 address, will send all available metrics to this server via the carbon protocol, which is used by graphite and metronome. You may specify an alternate port by appending :port, for example: 127.0.0.1:2004. See Metrics and Statistics.

chroot

  • Path to a Directory

If set, chroot to this directory for more security. See Security of the PowerDNS Recursor

Make sure that /dev/log is available from within the chroot. Logging will silently fail over time otherwise (on logrotate).

When using chroot, all other paths (except for config-dir) set in the configuration are relative to the new root.

When using chroot and the API (webserver), api-readonly must be set and api-config-dir unset.

When running on a system where systemd manages services, chroot does not work out of the box, as PowerDNS cannot use the NOTIFY_SOCKET. Either do not chroot on these systems or set the ‘Type’ of this service to ‘simple’ instead of ‘notify’ (refer to the systemd documentation on how to modify unit-files).

client-tcp-timeout

  • Integer
  • Default: 2

Time to wait for data from TCP clients.

config-dir

  • Path

Location of configuration directory (recursor.conf). Usually /etc/powerdns, but this depends on SYSCONFDIR during compile-time.

config-name

  • String
  • Default: unset

When running multiple recursors on the same server, read settings from recursor-name.conf, this will also rename the binary image.

cpu-map

New in version 4.1.0.

  • String
  • Default: unset

Set CPU affinity for worker threads, asking the scheduler to run those threads on a single CPU, or a set of CPUs. This parameter accepts a space separated list of thread-id=cpu-id, or thread-id=cpu-id-1,cpu-id-2,…,cpu-id-N. For example, to make the worker thread 0 run on CPU id 0 and the worker thread 1 on CPUs 1 and 2:

cpu-map=0=0 1=1,2

The number of worker threads is determined by the threads setting. If pdns-distributes-queries is set, an additional thread is started, assigned the id 0, and is the only one listening on client sockets and accepting queries, distributing them to the other worker threads afterwards.

Starting with version 4.2.0, the thread handling the control channel, the webserver and other internal stuff has been assigned id 0 and more than one distributor thread can be started using the distributor-threads setting, so the distributor threads if any are assigned id 1 and counting, and the other threads follow behind.

This parameter is only available on OS that provides the pthread_setaffinity_np() function.

daemon

  • Boolean
  • Default: no

Changed in version 4.0.0: Default is now “no”, was “yes” before.

Operate in the background.

delegation-only

  • Domains, comma separated

Which domains we only accept delegations from (a Verisign special).

disable-packetcache

  • Boolean
  • Default: no

Turn off the packet cache. Useful when running with Lua scripts that can not be cached.

disable-syslog

  • Boolean
  • Default: no

Do not log to syslog, only to stdout. Use this setting when running inside a supervisor that handles logging (like systemd). Note: do not use this setting in combination with daemon as all logging will disappear.

distributor-threads

New in version 4.2.0.

If pdns-distributes-queries is set, spawn this number of distributor threads on startup. Distributor threads handle incoming queries and distribute them to other threads based on a hash of the query, to maximize the cache hit ratio.

dnssec

New in version 4.0.0.

  • One of off, process-no-validate, process, log-fail, validate, String
  • Default: process-no-validate

Set the mode for DNSSEC processing:

off

No DNSSEC processing whatsoever. Ignore DO-bits in queries, don’t request any DNSSEC information from authoritative servers. This behaviour is similar to PowerDNS Recursor pre-4.0.

process-no-validate

Respond with DNSSEC records to clients that ask for it, set the DO bit on all outgoing queries. Don’t do any validation.

process

Respond with DNSSEC records to clients that ask for it, set the DO bit on all outgoing queries. Do validation for clients that request it (by means of the AD- bit or DO-bit in the query).

log-fail

Similar behaviour to process, but validate RRSIGs on responses and log bogus responses.

validate

Full blown DNSSEC validation. Send SERVFAIL to clients on bogus responses.

dnssec-log-bogus

  • Boolean
  • Default: no

Log every DNSSEC validation failure. Note: This is not logged per-query but every time records are validated as Bogus.

dont-query

  • Netmasks, comma separated
  • Default: 127.0.0.0/8, 10.0.0.0/8, 100.64.0.0/10, 169.254.0.0/16, 192.168.0.0/16, 172.16.0.0/12, ::1/128, fc00::/7, fe80::/10, 0.0.0.0/8, 192.0.0.0/24, 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, 240.0.0.0/4, ::/96, ::ffff:0:0/96, 100::/64, 2001:db8::/32

The DNS is a public database, but sometimes contains delegations to private IP addresses, like for example 127.0.0.1. This can have odd effects, depending on your network, and may even be a security risk. Therefore, the PowerDNS Recursor by default does not query private space IP addresses. This setting can be used to expand or reduce the limitations.

Queries to addresses for zones as configured in any of the settings forward-zones, forward-zones-file or forward-zones-recurse are performed regardless of these limitations.

ecs-add-for

New in version 4.2.0.

  • Comma separated list of netmasks
  • Default: 0.0.0.0/0, ::, !127.0.0.0/8, !10.0.0.0/8, !100.64.0.0/10, !169.254.0.0/16, !192.168.0.0/16, !172.16.0.0/12, !::1/128, !fc00::/7, !fe80::/10

List of requestor netmasks for which the requestor IP Address should be used as the EDNS Client Subnet for outgoing queries. Outgoing queries for requestors that do not match this list will use the ecs-scope-zero-address instead. Valid incoming ECS values from use-incoming-edns-subnet are not replaced.

Regardless of the value of this setting, ECS values are only sent for outgoing queries matching the conditions in the edns-subnet-whitelist setting. This setting only controls the actual value being sent.

This defaults to not using the requestor address inside RFC1918 and similar “private” IP address spaces.

ecs-ipv4-bits

New in version 4.1.0.

  • Integer
  • Default: 24

Number of bits of client IPv4 address to pass when sending EDNS Client Subnet address information.

ecs-ipv6-bits

New in version 4.1.0.

  • Integer
  • Default: 56

Number of bits of client IPv6 address to pass when sending EDNS Client Subnet address information.

ecs-scope-zero-address

New in version 4.1.0.

  • IPv4 or IPv6 Address
  • Default: empty

The IP address sent via EDNS Client Subnet to authoritative servers listed in edns-subnet-whitelist when use-incoming-edns-subnet is set and the query has an ECS source prefix-length set to 0. The default is to look for the first usable (not an any one) address in query-local-address then query-local-address6. If no suitable address is found, the recursor fallbacks to sending 127.0.0.1.

edns-outgoing-bufsize

  • Integer
  • Default: 1680

This is the value set for the EDNS0 buffer size in outgoing packets. Lower this if you experience timeouts.

edns-subnet-whitelist

  • Comma separated list of domain names and netmasks
  • Default: (none)

List of netmasks and domains that EDNS Client Subnet should be enabled for in outgoing queries.

For example, an EDNS Client Subnet option containing the address of the initial requestor (but see ecs-add-for) will be added to an outgoing query sent to server 192.0.2.1 for domain X if 192.0.2.1 matches one of the supplied netmasks, or if X matches one of the supplied domains. The initial requestor address will be truncated to 24 bits for IPv4 (see ecs-ipv4-bits) and to 56 bits for IPv6 (see ecs-ipv6-bits), as recommended in the privacy section of RFC 7871.

By default, this option is empty, meaning no EDNS Client Subnet information is sent.

entropy-source

  • Path
  • Default: /dev/urandom

PowerDNS can read entropy from a (hardware) source. This is used for generating random numbers which are very hard to predict. Generally on UNIX platforms, this source will be /dev/urandom, which will always supply random numbers, even if entropy is lacking. Change to /dev/random if PowerDNS should block waiting for enough entropy to arrive.

etc-hosts-file

  • Path
  • Default: /etc/hosts

The path to the /etc/hosts file, or equivalent. This file can be used to serve data authoritatively using export-etc-hosts.

export-etc-hosts

  • Boolean
  • Default: no

If set, this flag will export the host names and IP addresses mentioned in /etc/hosts.

export-etc-hosts-search-suffix

  • String

If set, all hostnames in the export-etc-hosts file are loaded in canonical form, based on this suffix, unless the name contains a ‘.’, in which case the name is unchanged. So an entry called ‘pc’ with export-etc-hosts-search-suffix='home.com' will lead to the generation of ‘pc.home.com’ within the recursor. An entry called ‘server1.home’ will be stored as ‘server1.home’, regardless of this setting.

forward-zones

  • ‘zonename=IP’ pairs, comma separated

Queries for zones listed here will be forwarded to the IP address listed. i.e.

forward-zones=example.org=203.0.113.210, powerdns.com=2001:DB8::BEEF:5

Multiple IP addresses can be specified and port numbers other than 53 can be configured:

forward-zones=example.org=203.0.113.210:5300;127.0.0.1, powerdns.com=127.0.0.1;198.51.100.10:530;[2001:DB8::1:3]:5300

Forwarded queries have the ‘recursion desired’ bit set to 0, meaning that this setting is intended to forward queries to authoritative servers.

IMPORTANT: When using DNSSEC validation (which is default), forwards to non-delegated (e.g. internal) zones that have a DNSSEC signed parent zone will validate as Bogus. To prevent this, add a Negative Trust Anchor (NTA) for this zone in the lua-config-file with addNTA("your.zone", "A comment"). If this forwarded zone is signed, instead of adding NTA, add the DS record to the lua-config-file. See the DNSSEC in the PowerDNS Recursor information.

forward-zones-file

  • Path

Same as forward-zones, parsed from a file. Only 1 zone is allowed per line, specified as follows:

example.org=203.0.113.210, 192.0.2.4:5300

Zones prefixed with a ‘+’ are forwarded with the recursion-desired bit set, for which see forward-zones-recurse. Default behaviour without ‘+’ is as with forward-zones.

Changed in version 4.0.0: Comments are allowed, everything behind ‘#’ is ignored.

The DNSSEC notes from forward-zones apply here as well.

forward-zones-recurse

  • ‘zonename=IP’ pairs, comma separated

Like regular forward-zones, but forwarded queries have the ‘recursion desired’ bit set to 1, meaning that this setting is intended to forward queries to other recursive servers.

The DNSSEC notes from forward-zones apply here as well.

gettag-needs-edns-options

New in version 4.1.0.

  • Boolean
  • Default: no

If set, EDNS options in incoming queries are extracted and passed to the gettag() hook in the ednsoptions table.

hint-file

  • Path

If set, the root-hints are read from this file. If unset, default root hints are used.

include-dir

  • Path

Directory to scan for additional config files. All files that end with .conf are loaded in order using POSIX as locale.

latency-statistic-size

  • Integer
  • Default: 10000

Indication of how many queries will be averaged to get the average latency reported by the ‘qa-latency’ metric.

local-address

  • IP addresses, comma separated
  • Default: 127.0.0.1

Local IPv4 or IPv6 addresses to bind to. Addresses can also contain port numbers, for IPv4 specify like this: 192.0.2.4:5300, for IPv6: [::1]:5300.

Warning: When binding to wildcard addresses, UNIX semantics mean that answers may not be sent from the address a query was received on. It is highly recommended to bind to explicit addresses.

local-port

  • Integer
  • Default: 53

Local port to bind to. If an address in local-address does not have an explicit port, this port is used.

log-timestamp

New in version 4.1.0.

  • Bool
  • Default: yes

When printing log lines to stdout, prefix them with timestamps. Disable this if the process supervisor timestamps these lines already.

Note

The systemd unit file supplied with the source code already disables timestamp printing

non-local-bind

  • Boolean
  • Default: no

Bind to addresses even if one or more of the local-address’s do not exist on this server. Setting this option will enable the needed socket options to allow binding to non-local addresses. This feature is intended to facilitate ip-failover setups, but it may also mask configuration issues and for this reason it is disabled by default.

loglevel

  • Integer between 0 and 9
  • Default: 6

Amount of logging. Higher is more, more logging may destroy performance. It is recommended not to set this below 3.

log-common-errors

  • Boolean
  • Default: no

Some DNS errors occur rather frequently and are no cause for alarm.

log-rpz-changes

New in version 4.1.0.

  • Boolean
  • Default: no

Log additions and removals to RPZ zones at Info (6) level instead of Debug (7).

logging-facility

  • Integer

If set to a digit, logging is performed under this LOCAL facility. See Logging. Do not pass names like ‘local0’!

lowercase-outgoing

  • Boolean
  • Default: no

Set to true to lowercase the outgoing queries. When set to ‘no’ (the default) a query from a client using mixed case in the DNS labels (such as a user entering mixed-case names or draft-vixie-dnsext-dns0x20-00), PowerDNS preserves the case of the query. Broken authoritative servers might give a wrong or broken answer on this encoding. Setting lowercase-outgoing to ‘yes’ makes the PowerDNS Recursor lowercase all the labels in the query to the authoritative servers, but still return the proper case to the client requesting.

lua-config-file

  • Filename

If set, and Lua support is compiled in, this will load an additional configuration file for newer features and more complicated setups. See Lua Configuration for the options that can be set in this file.

lua-dns-script

  • Path
  • Default: unset

Path to a lua file to manipulate the Recursor’s answers. See Scripting The Recursor for more information.

lua-maintenance-interval

New in version 4.1.4.

  • Integer
  • Default: 1

The interval between calls to the Lua user defined maintenance() function in seconds. See Maintenance callback

max-cache-entries

  • Integer
  • Default: 1000000

Maximum number of DNS cache entries. 1 million per thread will generally suffice for most installations.

max-cache-ttl

  • Integer
  • Default: 86400

Maximum number of seconds to cache an item in the DNS cache, no matter what the original TTL specified.

Changed in version 4.1.0: The minimum value of this setting is 15. i.e. setting this to lower than 15 will make this value 15.

max-mthreads

  • Integer
  • Default: 2048

Maximum number of simultaneous MTasker threads.

max-packetcache-entries

  • Integer
  • Default: 500000

Maximum number of Packet Cache entries. 1 million per thread will generally suffice for most installations.

max-qperq

  • Integer
  • Default: 50

The maximum number of outgoing queries that will be sent out during the resolution of a single client query. This is used to limit endlessly chasing CNAME redirections.

max-negative-ttl

  • Integer
  • Default: 3600

A query for which there is authoritatively no answer is cached to quickly deny a record’s existence later on, without putting a heavy load on the remote server. In practice, caches can become saturated with hundreds of thousands of hosts which are tried only once. This setting, which defaults to 3600 seconds, puts a maximum on the amount of time negative entries are cached.

max-recursion-depth

  • Integer
  • Default: 40

Total maximum number of internal recursion calls the server may use to answer a single query. 0 means unlimited. The value of stack-size should be increased together with this one to prevent the stack from overflowing.

Changed in version 4.1.0: Before 4.1.0, this settings was unlimited.

max-tcp-clients

  • Integer
  • Default: 128

Maximum number of simultaneous incoming TCP connections allowed.

max-tcp-per-client

  • Integer
  • Default: 0 (unlimited)

Maximum number of simultaneous incoming TCP connections allowed per client (remote IP address).

max-tcp-queries-per-connection

New in version 4.1.0.

  • Integer
  • Default: 0 (unlimited)

Maximum number of DNS queries in a TCP connection.

max-total-msec

  • Integer
  • Default: 7000

Total maximum number of milliseconds of wallclock time the server may use to answer a single query.

max-udp-queries-per-round

New in version 4.1.4.

  • Integer
  • Default: 10000

Under heavy load the recursor might be busy processing incoming UDP queries for a long while before there is no more of these, and might therefore neglect scheduling new mthreads, handling responses from authoritative servers or responding to rec_control requests. This setting caps the maximum number of incoming UDP DNS queries processed in a single round of looping on recvmsg() after being woken up by the multiplexer, before returning back to normal processing and handling other events.

minimum-ttl-override

  • Integer
  • Default: 0 (disabled)

This setting artificially raises all TTLs to be at least this long. While this is a gross hack, and violates RFCs, under conditions of DoS, it may enable you to continue serving your customers. Can be set at runtime using rec_control set-minimum-ttl 3600.

new-domain-tracking

  • Boolean
  • Default: no (disabled)

Whether to track newly observed domains, i.e. never seen before. This is a probablistic algorithm, using a stable bloom filter to store records of previously seen domains. When enabled for the first time, all domains will appear to be newly observed, so the feature is best left enabled for e.g. a week or longer before using the results. Note that this feature is optional and must be enabled at compile-time, thus it may not be available in all pre-built packages. If protobuf is enabled and configured, then the newly observed domain status will appear as a flag in Response messages.

new-domain-log

  • Boolean
  • Default: yes (enabled)

If a newly observed domain is detected, log that domain in the recursor log file. The log line looks something like:

Jul 18 11:31:25 Newly observed domain nod=sdfoijdfio.com

new-domain-lookup

  • Domain Name
  • Example: nod.powerdns.com

If a domain is specified, then each time a newly observed domain is detected, the recursor will perform an A record lookup of “<newly observed domain>.<lookup domain>”. For example if ‘new-domain-lookup’ is configured as ‘nod.powerdns.com’, and a new domain ‘xyz123.tv’ is detected, then an A record lookup will be made for ‘xyz123.tv.nod.powerdns.com’. This feature gives a way to share the newly observed domain with partners, vendors or security teams. The result of the DNS lookup will be ignored by the recursor.

new-domain-db-size

  • Integer
  • Example: 67108864

The default size of the stable bloom filter used to store previously observed domains is 67108864. To change the number of cells, use this setting. For each cell, the SBF uses 1 bit of memory, and one byte of disk for the persistent file. If there are already persistent files saved to disk, this setting will have no effect unless you remove the existing files.

new-domain-history-dir

  • Path
  • Default: /var/lib/pdns-recursor/nod

This setting controls which directory is used to store the on-disk cache of previously observed domains.

The newly observed domain feature uses a stable bloom filter to store a history of previously observed domains. The data structure is synchronized to disk every 10 minutes, and is also initialized from disk on startup. This ensures that previously observed domains are preserved across recursor restarts. If you change the new-domain-db-size setting, you must remove any files from this directory.

new-domain-whitelist

  • List of Domain Names, comma separated
  • Example: xyz.com, abc.com

This setting is a list of all domains (and implicitly all subdomains) that will never be considered a new domain. For example, if the domain ‘xyz123.tv’ is in the list, then ‘foo.bar.xyz123.tv’ will never be considered a new domain. One use-case for the whitelist is to never reveal details of internal subdomains via the new-domain-lookup feature.

new-domain-pb-tag

  • String
  • Default: pnds-nod

If protobuf is configured, then this tag will be added to all protobuf response messages when a new domain is observed.

unique-response-tracking

  • Boolean
  • Default: no (disabled)

Whether to track unique DNS responses, i.e. never seen before combinations of the triplet (query name, query type, RR[rrname, rrtype, rrdata]). This can be useful for tracking potentially suspicious domains and behaviour, e.g. DNS fast-flux. If protobuf is enabled and configured, then the Protobuf Response message will contain a flag with udr set to true for each RR that is considered unique, i.e. never seen before. This feature uses a probabilistic data structure (stable bloom filter) to track unique responses, which can have false positives as well as false negatives, thus it is a best-effort feature. Increasing the number of cells in the SBF using the unique-response-db-size setting can reduce FPs and FNs.

unique-response-log

  • Boolean
  • Default: no (disabled)

Whether to log when a unique response is detected. The log line looks something like:

Oct 24 12:11:27 Unique response observed: qname=foo.com qtype=A rrtype=AAAA rrname=foo.com rrcontent=1.2.3.4

unique-response-db-size

  • Integer
  • Example: 67108864

The default size of the stable bloom filter used to store previously observed responses is 67108864. To change the number of cells, use this setting. For each cell, the SBF uses 1 bit of memory, and one byte of disk for the persistent file. If there are already persistent files saved to disk, this setting will have no effect unless you remove the existing files.

unique-response-history-dir

  • Path
  • Default: /var/lib/pdns-recursor/udr

This setting controls which directory is used to store the on-disk cache of previously observed responses.

The newly observed domain feature uses a stable bloom filter to store a history of previously observed responses. The data structure is synchronized to disk every 10 minutes, and is also initialized from disk on startup. This ensures that previously observed responses are preserved across recursor restarts. If you change the unique-response-db-size, you must remove any files from this directory.

unique-response-pb-tag

  • String
  • Default: pnds-udr

If protobuf is configured, then this tag will be added to all protobuf response messages when a unique DNS response is observed.

network-timeout

  • Integer
  • Default: 1500

Number of milliseconds to wait for a remote authoritative server to respond.

nsec3-max-iterations

New in version 4.1.0.

  • Integer
  • Default: 2500

Maximum number of iterations allowed for an NSEC3 record. If an answer containing an NSEC3 record with more iterations is received, its DNSSEC validation status is treated as Insecure.

packetcache-ttl

  • Integer
  • Default: 3600

Maximum number of seconds to cache an item in the packet cache, no matter what the original TTL specified.

packetcache-servfail-ttl

  • Integer
  • Default: 60

Maximum number of seconds to cache a ‘server failure’ answer in the packet cache.

Changed in version 4.0.0: This setting’s maximum is capped to packetcache-ttl. i.e. setting packetcache-ttl=15 and keeping packetcache-servfail-ttl at the default will lower packetcache-servfail-ttl to 15.

pdns-distributes-queries

  • Boolean
  • Default: yes

If set, PowerDNS will have only 1 thread listening on client sockets, and distribute work by itself over threads by using a hash of the query, maximizing the cache hit ratio. Starting with version 4.2.0, more than one distributing thread can be started using the distributor-threads setting. Improves performance on Linux.

query-local-address

  • IPv4 Address, comma separated
  • Default: 0.0.0.0

Send out local queries from this address, or addresses, by adding multiple addresses, increased spoofing resilience is achieved.

query-local-address6

  • IPv6 addresses, comma separated
  • Default: unset

Send out local IPv6 queries from this address or addresses. Disabled by default, which also disables outgoing IPv6 support.

quiet

  • Boolean
  • Default: yes

Don’t log queries.

reuseport

  • Boolean
  • Default: no

If SO_REUSEPORT support is available, allows multiple processes to open a listening socket on the same port.

Since 4.1.0, when pdns-distributes-queries is set to false and reuseport is enabled, every thread will open a separate listening socket to let the kernel distribute the incoming queries, avoiding any thundering herd issue as well as the distributor thread being a bottleneck, thus leading to much higher performance on multi-core boxes.

rng

  • String
  • Default: auto
Specify which random number generator to use. Permissible choises are
  • auto - choose automatically
  • sodium - Use libsodium randombytes_uniform
  • openssl - Use libcrypto RAND_bytes
  • getrandom - Use libc getrandom, falls back to urandom if it does not really work
  • arc4random - Use BSD arc4random_uniform
  • urandom - Use /dev/urandom
  • kiss - Use simple settable deterministic RNG. FOR TESTING PURPOSES ONLY!

Note

Not all choises are available on all systems.

root-nx-trust

  • Boolean
  • Default: yes

If set, an NXDOMAIN from the root-servers will serve as a blanket NXDOMAIN for the entire TLD the query belonged to. The effect of this is far fewer queries to the root-servers.

Changed in version 4.0.0: Default is ‘yes’ now, was ‘no’ before 4.0.0

security-poll-suffix

  • String
  • Default: secpoll.powerdns.com.

Domain name from which to query security update notifications. Setting this to an empty string disables secpoll.

serve-rfc1918

  • Boolean
  • Default: yes

This makes the server authoritatively aware of: 10.in-addr.arpa, 168.192.in-addr.arpa, 16-31.172.in-addr.arpa, which saves load on the AS112 servers. Individual parts of these zones can still be loaded or forwarded.

server-down-max-fails

  • Integer
  • Default: 64

If a server has not responded in any way this many times in a row, no longer send it any queries for server-down-throttle-time seconds. Afterwards, we will try a new packet, and if that also gets no response at all, we again throttle for server-down-throttle-time seconds. Even a single response packet will drop the block.

server-down-throttle-time

  • Integer
  • Default: 60

Throttle a server that has failed to respond server-down-max-fails times for this many seconds.

server-id

  • String
  • Default: The hostname of the server

The reply given by The PowerDNS recursor to a query for ‘id.server’ with its hostname, useful for in clusters. When a query contains the NSID EDNS0 Option, this value is returned in the response as the NSID value.

This setting can be used to override the answer given to these queries. Set to “disabled” to disable NSID and ‘id.server’ answers.

Query example (where 192.0.2.14 is your server):

dig @192.0.2.14 CHAOS TXT id.server.
dig @192.0.2.14 example.com IN A +nsid

setgid, setuid

  • String
  • Default: unset

PowerDNS can change its user and group id after binding to its socket. Can be used for better security.

signature-inception-skew

New in version 4.1.5.

  • Integer
  • Default: 60

Allow the signature inception to be off by this number of seconds. Negative values are not allowed.

Changed in version 4.2.0: Default is now 60, was 0 before.

single-socket

  • Boolean
  • Default: no

Use only a single socket for outgoing queries.

snmp-agent

New in version 4.1.0.

  • Boolean
  • Default: no

If set to true and PowerDNS has been compiled with SNMP support, it will register as an SNMP agent to provide statistics and be able to send traps.

snmp-master-socket

New in version 4.1.0.

  • String
  • Default: empty

If not empty and snmp-agent is set to true, indicates how PowerDNS should contact the SNMP master to register as an SNMP agent.

socket-dir

  • Path

Where to store the control socket and pidfile. The default depends on LOCALSTATEDIR during compile-time (usually /var/run or /run).

When using chroot the default becomes to /.

socket-owner, socket-group, socket-mode

Owner, group and mode of the controlsocket. Owner and group can be specified by name, mode is in octal.

spoof-nearmiss-max

  • Integer
  • Default: 20

If set to non-zero, PowerDNS will assume it is being spoofed after seeing this many answers with the wrong id.

stack-size

  • Integer
  • Default: 200000

Size of the stack per thread.

statistics-interval

New in version 4.1.0.

  • Integer
  • Default: 1800

Interval between logging statistical summary on recursor performance. Use 0 to disable.

stats-ringbuffer-entries

  • Integer
  • Default: 10000

Number of entries in the remotes ringbuffer, which keeps statistics on who is querying your server. Can be read out using rec_control top-remotes.

tcp-fast-open

New in version 4.1.0.

  • Integer
  • Default: 0 (Disabled)

Enable TCP Fast Open support, if available, on the listening sockets. The numerical value supplied is used as the queue size, 0 meaning disabled.

threads

  • Integer
  • Default: 2

Spawn this number of threads on startup.

trace

  • Boolean
  • Default: no

If turned on, output impressive heaps of logging. May destroy performance under load.

udp-source-port-min

New in version 4.2.0.

  • Integer
  • Default: 1024

This option sets the low limit of UDP port number to bind on.

In combination with udp-source-port-max it configures the UDP port range to use. Port numbers are randomized within this range on initialization, and exceptions can be configured with udp-source-port-avoid

udp-source-port-max

New in version 4.2.0.

  • Integer
  • Default: 65535

This option sets the maximum limit of UDP port number to bind on.

See udp-source-port-min.

udp-source-port-avoid

New in version 4.2.0.

  • String
  • Default: 11211

A list of comma-separated UDP port numbers to avoid when binding. Ex: 5300,11211

See udp-source-port-min.

udp-truncation-threshold

  • Integer
  • Default: 1680

EDNS0 allows for large UDP response datagrams, which can potentially raise performance. Large responses however also have downsides in terms of reflection attacks. This setting limits the accepted size. Maximum value is 65535, but values above 4096 should probably not be attempted.

use-incoming-edns-subnet

  • Boolean
  • Default: no

Whether to process and pass along a received EDNS Client Subnet to authoritative servers. The ECS information will only be sent for netmasks and domains listed in edns-subnet-whitelist and will be truncated if the received scope exceeds ecs-ipv4-bits for IPv4 or ecs-ipv6-bits for IPv6.

version

Print version of this binary. Useful for checking which version of the PowerDNS recursor is installed on a system.

version-string

  • String
  • Default: PowerDNS Recursor version number

By default, PowerDNS replies to the ‘version.bind’ query with its version number. Security conscious users may wish to override the reply PowerDNS issues.

webserver

  • Boolean
  • Default: no

Start the webserver (for REST API).

webserver-address

  • IP Address
  • Default: 127.0.0.1

IP address for the webserver to listen on.

webserver-allow-from

  • IP addresses, comma separated
  • Default: 127.0.0.1,::1

Changed in version 4.1.0: Default is now 127.0.0.1,::1, was 0.0.0.0,::/0 before.

These subnets are allowed to access the webserver.

webserver-password

  • String
  • Default: unset

Password required to access the webserver.

webserver-port

  • Integer
  • Default: 8082

TCP port where the webserver should listen on.

write-pid

  • Boolean
  • Default: yes

If a PID file should be written to socket-dir

xpf-allow-from

New in version 4.2.0.

  • IP ranges, separated by commas
  • Default: empty

Note

This is an experimental implementation of draft-bellis-dnsop-xpf.

The server will trust XPF records found in queries sent from those netmasks (both IPv4 and IPv6), and will adjust queries’ source and destination accordingly. This is especially useful when the recursor is placed behind a proxy like dnsdist. Note that the ref:setting-allow-from setting is still applied to the original source address, and thus access restriction should be done on the proxy.

xpf-rr-code

New in version 4.2.0.

  • Integer
  • Default: 0

Note

This is an experimental implementation of draft-bellis-dnsop-xpf.

This option sets the resource record code to use for XPF records, as long as an official code has not been assigned to it. 0 means that XPF is disabled.