1 Authoritative Server Settings
2 =============================
4 All PowerDNS Authoritative Server settings are listed here, excluding
5 those that originate from backends, which are documented in the relevant
6 chapters. These settings can be set inside ``pdns.conf`` or on the
7 commandline when invoking the ``pdns`` binary.
9 You can use ``+=`` syntax to set some variables incrementally, but this
10 requires you to have at least one non-incremental setting for the
11 variable to act as base setting. This is mostly useful for
12 :ref:`setting-include-dir` directive.
14 For boolean settings, specifying the name of the setting without a value
25 .. versionadded:: 4.0.0
27 Allow 8 bit DNS queries.
29 .. _setting-allow-axfr-ips:
34 - IP ranges, separated by commas
35 - Default: 127.0.0.0/8,::1
37 If set, only these IP addresses or netmasks will be able to perform
40 .. _setting-allow-dnsupdate-from:
42 ``allow-dnsupdate-from``
43 ------------------------
45 - IP ranges, separated by commas
46 - Default: 127.0.0.0/8,::1
48 Allow DNS updates from these IP ranges. Set to empty string to honour ``ALLOW-DNSUPDATE-FROM`` in :ref:`metadata-allow-dnsupdate-from`.
50 .. _setting-allow-notify-from:
55 - IP ranges, separated by commas
56 - Default: 0.0.0.0/0,::/0
58 Allow AXFR NOTIFY from these IP ranges. Setting this to an empty string
59 will drop all incoming notifies.
61 .. _setting-allow-recursion:
66 - IP ranges, separated by commas
70 Recursion has been removed, see :doc:`guides/recursion`
72 By specifying ``allow-recursion``, recursion can be restricted to
73 netmasks specified. The default is to allow recursion from everywhere.
74 Example: ``allow-recursion=198.51.100.0/24, 10.0.0.0/8, 192.0.2.4``.
76 .. _setting-allow-unsigned-notify:
78 ``allow-unsigned-notify``
79 -------------------------
84 .. versionadded:: 4.0.0
86 Turning this off requires all notifications that are received to be
87 signed by valid TSIG signature for the zone.
89 .. _setting-allow-unsigned-supermaster:
91 ``allow-unsigned-supermaster``
92 ------------------------------
97 .. versionadded:: 4.0.0
99 Turning this off requires all supermaster notifications to be signed by
100 valid TSIG signature. It will accept any existing key on slave.
102 .. _setting-also-notify:
107 - IP addresses, separated by commas
109 When notifying a domain, also notify these nameservers. Example:
110 ``also-notify=192.0.2.1, 203.0.113.167``. The IP addresses listed in
111 ``also-notify`` always receive a notification. Even if they do not match
112 the list in :ref:`setting-only-notify`.
114 .. _setting-any-to-tcp:
122 .. versionchanged:: 4.0.1
125 Answer questions for the ANY on UDP with a truncated packet that refers
126 the remote server to TCP. Useful for mitigating reflection attacks.
136 Enable/disable the :doc:`http-api/index`.
145 .. versionadded:: 4.0.0
147 Static pre-shared authentication key for access to the REST API.
149 .. _setting-api-readonly:
157 .. versionadded:: 4.0.0
158 .. versionchanged:: 4.2.0
159 This setting has been removed in 4.2.0.
161 Disallow data modification through the REST API when set.
163 .. _setting-axfr-fetch-timeout:
165 ``axfr-fetch-timeout``
166 ----------------------
171 .. versionadded:: 4.3.0
173 Maximum time in seconds for inbound AXFR to start or be idle after starting.
175 .. _setting-axfr-lower-serial:
177 ``axfr-lower-serial``
178 ---------------------
183 .. versionadded:: 4.0.4
185 Also AXFR a zone from a master with a lower serial.
187 .. _setting-cache-ttl:
195 Seconds to store packets in the :ref:`packet-cache`. A value of 0 will disable the cache.
197 .. _setting-carbon-instance:
205 .. versionadded:: 4.2.0
207 Set the instance or third string of the metric key. Be careful not to include
208 any dots in this setting, unless you know what you are doing.
209 See :ref:`metricscarbon`
211 .. _setting-carbon-interval:
219 If sending carbon updates, this is the interval between them in seconds.
220 See :ref:`metricscarbon`.
222 .. _setting-carbon-namespace:
230 .. versionadded:: 4.2.0
232 Set the namespace or first string of the metric key. Be careful not to include
233 any dots in this setting, unless you know what you are doing.
234 See :ref:`metricscarbon`
236 .. _setting-carbon-ourname:
242 - Default: the hostname of the server
244 If sending carbon updates, if set, this will override our hostname. Be
245 careful not to include any dots in this setting, unless you know what
246 you are doing. See :ref:`metricscarbon`
248 .. _setting-carbon-server:
255 Send all available metrics to this server via the carbon protocol, which
256 is used by graphite and metronome. It has to be an address (no
257 hostnames). Moreover you can specify more than one server using a comma delimited list, ex:
258 carbon-server=10.10.10.10,10.10.10.20.
259 You may specify an alternate port by appending :port, ex:
260 127.0.0.1:2004. See :ref:`metricscarbon`.
269 If set, chroot to this directory for more security. See :doc:`security`.
271 Make sure that ``/dev/log`` is available from within the chroot. Logging
272 will silently fail over time otherwise (on logrotate).
274 When setting ``chroot``, all other paths in the config (except for
275 :ref:`setting-config-dir` and :ref:`setting-module-dir`)
276 set in the configuration are relative to the new root.
278 When running on a system where systemd manages services, ``chroot`` does
279 not work out of the box, as PowerDNS cannot use the ``NOTIFY_SOCKET``.
280 Either don't ``chroot`` on these systems or set the 'Type' of the this
281 service to 'simple' instead of 'notify' (refer to the systemd
282 documentation on how to modify unit-files)
284 .. _setting-config-dir:
291 Location of configuration directory (``pdns.conf``). Usually
292 ``/etc/powerdns``, but this depends on ``SYSCONFDIR`` during
295 .. _setting-config-name:
302 Name of this virtual configuration - will rename the binary image. See
303 :doc:`guides/virtual-instances`.
305 .. _setting-control-console:
310 Debugging switch - don't use.
322 .. _setting-default-api-rectify:
324 ``default-api-rectify``
325 -----------------------
329 .. versionadded:: 4.2.0
331 The value of :ref:`metadata-api-rectify` if it is not set on the zone.
334 Pre 4.2.0 the default was always no.
336 .. _setting-default-ksk-algorithms:
337 .. _setting-default-ksk-algorithm:
339 ``default-ksk-algorithm``
340 -------------------------
345 .. versionchanged:: 4.1.0
346 Renamed from ``default-ksk-algorithms``. No longer supports multiple algorithm names.
348 The algorithm that should be used for the KSK when running
349 :doc:`pdnsutil secure-zone <manpages/pdnsutil.1>` or using the :doc:`Zone API endpoint <http-api/cryptokey>`
350 to enable DNSSEC. Must be one of:
355 * ecdsa256 (ECDSA P-256 with SHA256)
356 * ecdsa384 (ECDSA P-384 with SHA384)
361 Actual supported algorithms depend on the crypto-libraries
362 PowerDNS was compiled against. To check the supported DNSSEC algoritms
363 in your build of PowerDNS, run ``pdnsutil list-algorithms``.
365 .. _setting-default-ksk-size:
371 - Default: whichever is default for `default-ksk-algorithm`_
373 The default keysize for the KSK generated with :doc:`pdnsutil secure-zone <dnssec/pdnsutil>`.
374 Only relevant for algorithms with non-fixed keysizes (like RSA).
376 .. _setting-default-soa-edit:
384 Use this soa-edit value for all zones if no
385 :ref:`metadata-soa-edit` metadata value is set.
387 .. _setting-default-soa-edit-signed:
389 ``default-soa-edit-signed``
390 ---------------------------
395 Use this soa-edit value for all signed zones if no
396 :ref:`metadata-soa-edit` metadata value is set.
397 Overrides :ref:`setting-default-soa-edit`
399 .. _setting-default-soa-mail:
406 .. deprecated:: 4.2.0
407 This setting has been deprecated and will be removed in 4.3.0
409 Mail address to insert in the SOA record if none set in the backend.
411 .. _setting-default-soa-name:
417 - Default: a.misconfigured.powerdns.server
419 .. deprecated:: 4.2.0
420 This setting has been deprecated and will be removed in 4.3.0
422 Name to insert in the SOA record if none set in the backend.
424 .. _setting-default-ttl:
432 TTL to use when none is provided.
434 .. _setting-default-zsk-algorithms:
435 .. _setting-default-zsk-algorithm:
437 ``default-zsk-algorithm``
438 --------------------------
443 .. versionchanged:: 4.1.0
444 Renamed from ``default-zsk-algorithms``. Does no longer support multiple algorithm names.
446 The algorithm that should be used for the ZSK when running
447 :doc:`pdnsutil secure-zone <manpages/pdnsutil.1>` or using the :doc:`Zone API endpoint <http-api/cryptokey>`
448 to enable DNSSEC. Must be one of:
453 * ecdsa256 (ECDSA P-256 with SHA256)
454 * ecdsa384 (ECDSA P-384 with SHA384)
459 Actual supported algorithms depend on the crypto-libraries
460 PowerDNS was compiled against. To check the supported DNSSEC algoritms
461 in your build of PowerDNS, run ``pdnsutil list-algorithms``.
463 .. _setting-default-zsk-size:
469 - Default: 0 (automatic default for `default-zsk-algorithm`_)
471 The default keysize for the ZSK generated with :doc:`pdnsutil secure-zone <dnssec/pdnsutil>`.
472 Only relevant for algorithms with non-fixed keysizes (like RSA).
474 .. _setting-direct-dnskey:
482 Read additional DNSKEY, CDS and CDNSKEY records from the records table/your BIND zonefile. If not
483 set, DNSKEY, CDS and CDNSKEY records in the zonefiles are ignored.
485 .. _setting-disable-axfr:
493 Do not allow zone transfers.
495 .. _setting-disable-axfr-rectify:
497 ``disable-axfr-rectify``
498 ------------------------
503 Disable the rectify step during an outgoing AXFR. Only required for
506 .. _setting-disable-syslog:
514 Do not log to syslog, only to stdout. Use this setting when running
515 inside a supervisor that handles logging (like systemd).
518 Do not use this setting in combination with :ref:`setting-daemon` as all
519 logging will disappear.
521 .. _setting-disable-tcp:
529 .. versionchanged:: 4.2.0
530 This setting has been removed
532 Do not listen to TCP queries. Breaks RFC compliance.
534 .. _setting-distributor-threads:
536 ``distributor-threads``
537 -----------------------
542 Number of Distributor (backend) threads to start per receiver thread.
543 See :doc:`performance`.
545 .. _setting-dname-processing:
553 Synthesise CNAME records from DNAME records as required. This
554 approximately doubles query load. **Do not combine with DNSSEC!**
556 .. _setting-dnssec-key-cache-ttl:
558 ``dnssec-key-cache-ttl``
559 ------------------------
564 Seconds to cache DNSSEC keys from the database. A value of 0 disables
567 .. _setting-dnsupdate:
575 Enable/Disable DNS update (RFC2136) support. See :doc:`dnsupdate` for more.
577 .. _setting-do-ipv6-additional-processing:
579 ``do-ipv6-additional-processing``
580 ---------------------------------
585 Perform AAAA additional processing. This sends AAAA records in the
586 ADDITIONAL section when sending a referral.
588 .. _setting-domain-metadata-cache-ttl:
590 ``domain-metadata-cache-ttl``
591 -----------------------------
596 Seconds to cache domain metadata from the database. A value of 0
599 .. _setting-edns-subnet-processing:
601 ``edns-subnet-processing``
602 --------------------------
607 Enables EDNS subnet processing, for backends that support it.
609 .. _setting-enable-lua-records:
611 ``enable-lua-records``
612 ----------------------
614 - One of ``no``, ``yes`` (or empty), or ``shared``, String
617 .. versionadded:: 4.2.0
619 Globally enable the :doc:`LUA records <lua-records/index>` feature.
621 To use shared LUA states, set this to ``shared``, see :ref:`lua-records-shared-state`.
623 .. _setting-entropy-source:
629 - Default: /dev/urandom
631 Entropy source file to use.
633 .. _setting-expand-alias:
641 .. versionadded:: 4.1.0
643 If this is enabled, ALIAS records are expanded (synthesised to their
646 If this is disabled (the default), ALIAS records will not be expanded and
647 the server will will return NODATA for A/AAAA queries for such names.
650 :ref:`setting-resolver` must also be set for ALIAS expansion to work!
653 In PowerDNS Authoritative Server 4.0.x, this setting did not exist and
654 ALIAS was always expanded.
656 .. _setting-forward-dnsupdate:
658 ``forward-dnsupdate``
659 ---------------------
664 Forward DNS updates sent to a slave to the master.
666 .. _setting-forward-notify:
671 - IP addresses, separated by commas
673 IP addresses to forward received notifications to regardless of master
677 The intended use is in anycast environments where it might be
678 necessary for a proxy server to perform the AXFR. The usual checks are
679 performed before any received notification is forwarded.
681 .. _setting-guardian:
689 Run within a guardian process. See :ref:`running-guardian`.
691 .. _setting-include-dir:
698 Directory to scan for additional config files. All files that end with
699 .conf are loaded in order using ``POSIX`` as locale.
706 - Backend names, separated by commas
708 Which backends to launch and order to query them in. Launches backends.
709 In its most simple form, supply all backends that need to be launched.
714 launch=bind,gmysql,remote
716 If you find that you need to query a backend multiple times with
717 different configuration, you can specify a name for later
718 instantiations. e.g.:
722 launch=gmysql,gmysql:server2
724 In this case, there are 2 instances of the gmysql backend, one by the
725 normal name and the second one is called 'server2'. The backend
726 configuration item names change: e.g. ``gmysql-host`` is available to
727 configure the ``host`` setting of the first or main instance, and
728 ``gmysql-server2-host`` for the second one.
730 Running multiple instances of the BIND backend is not allowed.
732 .. _setting-load-modules:
737 - Paths, separated by commas
739 If backends are available in nonstandard directories, specify their
740 location here. Multiple files can be loaded if separated by commas. Only
741 available in non-static distributions.
743 .. _setting-local-address:
748 .. versionchanged:: 4.3.0
749 Before 4.3.0, this setting only supported IPv4.
751 - IPv4 Addresses, separated by commas or whitespace
752 - Default: 0.0.0.0, ``::``
754 Local IP addresses to which we bind. It is highly advised to bind to
755 specific interfaces and not use the default 'bind to any'. This causes
756 big problems if you have multiple IP addresses. Unix does not provide a
757 way of figuring out what IP address a packet was sent to when binding to
760 .. _setting-local-address-nonexist-fail:
762 ``local-address-nonexist-fail``
763 -------------------------------
768 Fail to start if one or more of the
769 :ref:`setting-local-address`'s do not exist on this server.
771 .. _setting-local-ipv6:
776 .. deprecated:: 4.3.0
777 This setting has been removed, use :ref:`setting-localaddress`
779 - IPv6 Addresses, separated by commas or whitespace
782 Local IPv6 address to which we bind. It is highly advised to bind to
783 specific interfaces and not use the default 'bind to any'. This causes
784 big problems if you have multiple IP addresses.
786 .. _setting-local-ipv6-nonexist-fail:
788 ``local-ipv6-nonexist-fail``
789 ----------------------------
791 .. deprecated:: 4.3.0
792 This setting has been removed, use :ref:`setting-localaddress-nonexist-fail`
797 Fail to start if one or more of the :ref:`setting-local-ipv6`
798 addresses do not exist on this server.
800 .. _setting-local-port:
808 The port on which we listen. Only one port possible.
810 .. _setting-log-dns-details:
818 If set to 'no', informative-only DNS details will not even be sent to
819 syslog, improving performance.
821 .. _setting-log-dns-queries:
829 Tell PowerDNS to log all incoming DNS queries. This will lead to a lot
830 of logging! Only enable for debugging! Set :ref:`setting-loglevel`
831 to at least 5 to see the logs.
833 .. _setting-log-timestamp:
841 .. versionadded:: 4.1.0
843 When printing log lines to stdout, prefix them with timestamps.
844 Disable this if the process supervisor timestamps these lines already.
847 The systemd unit file supplied with the source code already disables timestamp printing
849 .. _setting-logging-facility:
854 If set to a digit, logging is performed under this LOCAL facility. See :ref:`logging-to-syslog`.
855 Do not pass names like 'local0'!
857 .. _setting-loglevel:
865 Amount of logging. Higher is more. Do not set below 3. Corresponds to "syslog" level values,
866 e.g. error = 3, warning = 4, notice = 5, info = 6
868 .. _setting-lua-axfr-script:
876 .. versionadded:: 4.1.0
878 Script to be used to edit incoming AXFRs, see :ref:`modes-of-operation-axfrfilter`
880 .. _setting-lua-prequery-script:
882 ``lua-prequery-script``
883 -----------------------
887 Lua script to run before answering a query. This is a feature used
888 internally for regression testing. The API of this functionality is not
889 guaranteed to be stable, and is in fact likely to change.
891 .. _setting-lua-records-exec-limit:
893 ``lua-records-exec-limit``
894 -----------------------------
899 Limit LUA records scripts to ``lua-records-exec-limit`` instructions.
900 Setting this to any value less than or equal to 0 will set no limit.
910 Turn on master support. See :ref:`master-operation`.
912 .. _setting-max-cache-entries:
914 ``max-cache-entries``
915 ---------------------
920 .. versionchanged:: 4.1.0
921 The packet and query caches are distinct. Previously, this setting was used for
922 both the packet and query caches. See :ref:`setting-max-packet-cache-entries` for
923 the packet-cache setting.
925 Maximum number of entries in the query cache. 1 million (the default)
926 will generally suffice for most installations.
928 .. _setting-max-ent-entries:
936 Maximum number of empty non-terminals to add to a zone. This is a
937 protection measure to avoid database explosion due to long names.
939 .. _setting-max-generate-steps:
941 ``max-generate-steps``
942 ----------------------
944 .. versionadded:: 4.3.0
949 Maximum number of steps for a '$GENERATE' directive when parsing a
950 zone file. This is a protection measure to prevent consuming a lot of
951 CPU and memory when untrusted zones are loaded. Default to 0 which
954 .. _setting-max-nsec3-iterations:
956 ``max-nsec3-iterations``
957 ------------------------
962 Limit the number of NSEC3 hash iterations for zone configurations.
963 For more information see :ref:`dnssec-operational-nsec-modes-params`.
965 .. _setting-max-packet-cache-entries:
967 ``max-packet-cache-entries``
968 ----------------------------
973 .. versionadded:: 4.1.0
975 Maximum number of entries in the packet cache. 1 million (the default)
976 will generally suffice for most installations.
978 .. _setting-max-queue-length:
986 If this many packets are waiting for database attention, consider the
987 situation hopeless and respawn.
989 .. _setting-max-signature-cache-entries:
991 ``max-signature-cache-entries``
992 -------------------------------
995 - Default: 2^31-1 (on most systems), 2^63-1 (on ILP64 systems)
997 Maximum number of signatures cache entries
999 .. _setting-max-tcp-connection-duration:
1001 ``max-tcp-connection-duration``
1002 -------------------------------
1007 Maximum time in seconds that a TCP DNS connection is allowed to stay
1008 open. 0 means unlimited. Note that exchanges related to an AXFR or IXFR
1009 are not affected by this setting.
1011 .. _setting-max-tcp-connections:
1013 ``max-tcp-connections``
1014 -----------------------
1019 Allow this many incoming TCP DNS connections simultaneously.
1021 .. _setting-max-tcp-connections-per-client:
1023 ``max-tcp-connections-per-client``
1024 ----------------------------------
1029 Maximum number of simultaneous TCP connections per client. 0 means
1032 .. _setting-max-tcp-transactions-per-conn:
1034 ``max-tcp-transactions-per-conn``
1035 ---------------------------------
1040 Allow this many DNS queries in a single TCP transaction. 0 means
1041 unlimited. Note that exchanges related to an AXFR or IXFR are not
1042 affected by this setting.
1044 .. _setting-module-dir:
1051 Directory for modules. Default depends on ``PKGLIBDIR`` during
1054 .. _setting-negquery-cache-ttl:
1056 ``negquery-cache-ttl``
1057 ----------------------
1062 Seconds to store queries with no answer in the Query Cache. See :ref:`query-cache`.
1064 .. _setting-no-config:
1072 Do not attempt to read the configuration file. Useful for configuration
1073 by parameters from the command line only.
1075 .. _setting-no-shuffle:
1083 Do not attempt to shuffle query results, used for regression testing.
1085 .. _setting-non-local-bind:
1093 Bind to addresses even if one or more of the
1094 :ref:`setting-local-address`'s do not exist on this server.
1095 Setting this option will enable the needed socket options to allow
1096 binding to non-local addresses. This feature is intended to facilitate
1097 ip-failover setups, but it may also mask configuration issues and for
1098 this reason it is disabled by default.
1100 .. _setting-only-notify:
1105 - IP Ranges, separated by commas or whitespace
1106 - Default: 0.0.0.0/0, ::/0
1108 For type=MASTER zones (or SLAVE zones with slave-renotify enabled)
1109 PowerDNS automatically sends NOTIFYs to the name servers specified in
1110 the NS records. By specifying networks/mask as whitelist, the targets
1111 can be limited. The default is to notify the world. To completely
1112 disable these NOTIFYs set ``only-notify`` to an empty value. Independent
1113 of this setting, the IP addresses or netmasks configured with
1114 :ref:`setting-also-notify` and ``ALSO-NOTIFY`` domain metadata
1115 always receive AXFR NOTIFYs.
1117 IP addresses and netmasks can be excluded by prefixing them with a ``!``.
1118 To notify all IP addresses apart from the 192.168.0.0/24 subnet use the following::
1120 only-notify=0.0.0.0/0, ::/0, !192.168.0.0/24
1123 Even if NOTIFYs are limited by a netmask, PowerDNS first has to
1124 resolve all the hostnames to check their IP addresses against the
1125 specified whitelist. The resolving may take considerable time,
1126 especially if those hostnames are slow to resolve. If you do not need to
1127 NOTIFY the slaves defined in the NS records (e.g. you are using another
1128 method to distribute the zone data to the slaves), then set
1129 :ref:`setting-only-notify` to an empty value and specify the notification targets
1130 explicitly using :ref:`setting-also-notify` and/or
1131 :ref:`metadata-also-notify` domain metadata to avoid this potential bottleneck.
1134 If your slaves support an Internet Protocol version, which your master does not,
1135 then set ``only-notify`` to include only supported protocol version.
1136 Otherwise there will be error trying to resolve address.
1138 For example, slaves support both IPv4 and IPv6, but PowerDNS master have only IPv4,
1139 so allow only IPv4 with ``only-notify``:
1143 only-notify=0.0.0.0/0
1145 .. _setting-out-of-zone-additional-processing:
1147 ``out-of-zone-additional-processing``
1148 -------------------------------------
1153 .. deprecated:: 4.2.0
1154 This setting has been removed.
1156 Do out of zone additional processing. This means that if a malicious
1157 user adds a '.com' zone to your server, it is not used for other domains
1158 and will not contaminate answers. Do not enable this setting if you run
1159 a public DNS service with untrusted users.
1161 The docs had previously indicated that the default was "no", but the
1162 default has been "yes" since 2005.
1164 .. _setting-outgoing-axfr-expand-alias:
1166 ``outgoing-axfr-expand-alias``
1167 ------------------------------
1172 If this is enabled, ALIAS records are expanded (synthesised to their
1173 A/AAAA) during outgoing AXFR. This means slaves will not automatically
1174 follow changes in those A/AAAA records unless you AXFR regularly!
1176 If this is disabled (the default), ALIAS records are sent verbatim
1177 during outgoing AXFR. Note that if your slaves do not support ALIAS,
1178 they will return NODATA for A/AAAA queries for such names.
1180 .. _setting-overload-queue-length:
1182 ``overload-queue-length``
1183 -------------------------
1186 - Default: 0 (disabled)
1188 If this many packets are waiting for database attention, answer any new
1189 questions strictly from the packet cache.
1191 .. _setting-prevent-self-notification:
1193 ``prevent-self-notification``
1194 -----------------------------
1199 PowerDNS Authoritative Server attempts to not send out notifications to
1200 itself in master mode. In very complicated situations we could guess
1201 wrong and not notify a server that should be notified. In that case, set
1202 prevent-self-notification to "no".
1204 .. _setting-query-cache-ttl:
1212 Seconds to store queries with an answer in the Query Cache. See :ref:`query-cache`.
1214 .. _setting-query-local-address:
1216 ``query-local-address``
1217 -----------------------
1222 The IP address to use as a source address for sending queries. Useful if
1223 you have multiple IPs and PowerDNS is not bound to the IP address your
1224 operating system uses by default for outgoing packets.
1226 .. _setting-query-local-address6:
1228 ``query-local-address6``
1229 ------------------------
1234 Source IP address for sending IPv6 queries.
1236 .. _setting-query-logging:
1244 Boolean, hints to a backend that it should log a textual representation
1245 of queries it performs. Can be set at runtime.
1247 .. _setting-queue-limit:
1255 Maximum number of milliseconds to queue a query. See :doc:`performance`.
1257 .. _setting-receiver-threads:
1259 ``receiver-threads``
1260 --------------------
1265 Number of receiver (listening) threads to start. See :doc:`performance`.
1267 .. _setting-recursive-cache-ttl:
1269 ``recursive-cache-ttl``
1270 -----------------------
1275 .. deprecated:: 4.1.0
1276 Recursion has been removed, see :doc:`guides/recursion`
1278 Seconds to store recursive packets in the :ref:`packet-cache`.
1280 .. _setting-recursor:
1287 .. deprecated:: 4.1.0
1288 Recursion has been removed, see :doc:`guides/recursion`
1290 If set, recursive queries will be handed to the recursor specified here.
1292 .. _setting-resolver:
1297 - IP Addresses with optional port, separated by commas
1299 .. versionadded:: 4.1.0
1301 Use these resolver addresses for ALIAS and the internal stub resolver.
1302 If this is not set, ``/etc/resolv.conf`` is parsed for upstream
1305 .. _setting-retrieval-threads:
1307 ``retrieval-threads``
1308 ---------------------
1313 Number of AXFR slave threads to start.
1315 .. _setting-reuseport:
1323 On Linux 3.9 and some BSD kernels the ``SO_REUSEPORT`` option allows
1324 each receiver-thread to open a new socket on the same port which allows
1325 for much higher performance on multi-core boxes. Setting this option
1326 will enable use of ``SO_REUSEPORT`` when available and seamlessly fall
1327 back to a single socket when it is not available. A side-effect is that
1328 you can start multiple servers on the same IP/port combination which may
1329 or may not be a good idea. You could use this to enable transparent
1330 restarts, but it may also mask configuration issues and for this reason
1331 it is disabled by default.
1341 Specify which random number generator to use. Permissible choises are:
1343 - auto - choose automatically
1344 - sodium - Use libsodium ``randombytes_uniform``
1345 - openssl - Use libcrypto ``RAND_bytes``
1346 - getrandom - Use libc getrandom, falls back to urandom if it does not really work
1347 - arc4random - Use BSD ``arc4random_uniform``
1348 - urandom - Use ``/dev/urandom``
1349 - kiss - Use simple settable deterministic RNG. **FOR TESTING PURPOSES ONLY!**
1352 Not all choises are available on all systems.
1354 .. _setting-security-poll-suffix:
1356 ``security-poll-suffix``
1357 ------------------------
1360 - Default: secpoll.powerdns.com.
1362 Domain name from which to query security update notifications. Setting
1363 this to an empty string disables secpoll.
1365 .. _setting-send-signed-notify:
1367 ``send-signed-notify``
1368 ----------------------
1373 If yes, outgoing NOTIFYs will be signed if a TSIG key is configured for the zone.
1374 If there are multiple TSIG keys configured for a domain, PowerDNS will use the
1375 first one retrieved from the backend, which may not be the correct one for the
1376 respective slave. Hence, in setups with multiple slaves with different TSIG keys
1377 it may be required to send NOTIFYs unsigned.
1379 .. _setting-server-id:
1385 - Default: The hostname of the server
1387 This is the server ID that will be returned on an EDNS NSID query.
1396 If set, change group id to this gid for more security. See :doc:`security`.
1405 If set, change user id to this uid for more security. See :doc:`security`.
1407 .. _setting-signing-threads:
1415 Tell PowerDNS how many threads to use for signing. It might help improve
1416 signing speed by changing this number.
1426 Turn on slave support. See :ref:`slave-operation`.
1428 .. _setting-slave-cycle-interval:
1430 ``slave-cycle-interval``
1431 ------------------------
1436 On a master, this is the amount of seconds between the master checking
1437 the SOA serials in its database to determine to send out NOTIFYs to the
1438 slaves. On slaves, this is the number of seconds between the slave
1439 checking for updates to zones.
1441 .. _setting-slave-renotify:
1449 This setting will make PowerDNS renotify the slaves after an AXFR is
1450 *received* from a master. This is useful when using when running a
1453 See :ref:`metadata-slave-renotify` to set this per-zone.
1455 .. _setting-soa-expire-default:
1457 ``soa-expire-default``
1458 ----------------------
1463 .. deprecated:: 4.2.0
1464 This setting has been deprecated and will be removed in 4.3.0
1466 Default :ref:`types-soa` expire.
1468 .. _setting-soa-minimum-ttl:
1476 .. deprecated:: 4.2.0
1477 This setting has been deprecated and will be removed in 4.3.0
1479 Default :ref:`types-soa` minimum ttl.
1481 .. _setting-soa-refresh-default:
1483 ``soa-refresh-default``
1484 -----------------------
1489 .. deprecated:: 4.2.0
1490 This setting has been deprecated and will be removed in 4.3.0
1492 Default :ref:`types-soa` refresh.
1494 .. _setting-soa-retry-default:
1496 ``soa-retry-default``
1497 ---------------------
1502 .. deprecated:: 4.2.0
1503 This setting has been deprecated and will be removed in 4.3.0
1505 Default :ref:`types-soa` retry.
1507 .. _setting-socket-dir:
1514 Where the controlsocket will live. The default depends on
1515 ``LOCALSTATEDIR`` during compile-time (usually ``/var/run`` or
1516 ``/run``). See :ref:`control-socket`.
1518 This path will also contain the pidfile for this instance of PowerDNS
1519 called ``pdns.pid`` by default. See :ref:`setting-config-name`
1520 and :doc:`Virtual Hosting <guides/virtual-instances>` how this can differ.
1522 .. _setting-superslave:
1530 .. versionadded:: 4.1.9
1531 In versions before 4.1.9, this setting did not exist and supermaster support
1532 was enabled by default.
1534 .. versionchanged:: 4.2.0
1535 Before 4.2.0, the default was yes.
1537 Turn on supermaster support. See :ref:`supermaster-operation`.
1539 .. _setting-tcp-control-address:
1541 ``tcp-control-address``
1542 -----------------------
1546 Address to bind to for TCP control.
1548 .. _setting-tcp-control-port:
1550 ``tcp-control-port``
1551 --------------------
1556 Port to bind to for TCP control.
1558 .. _setting-tcp-control-range:
1560 ``tcp-control-range``
1561 ---------------------
1563 - IP Ranges, separated by commas or whitespace
1565 Limit TCP control to a specific client range.
1567 .. _setting-tcp-control-secret:
1569 ``tcp-control-secret``
1570 ----------------------
1574 Password for TCP control.
1576 .. _setting-tcp-fast-open:
1582 - Default: 0 (Disabled)
1584 .. versionadded:: 4.1.0
1586 Enable TCP Fast Open support, if available, on the listening sockets.
1587 The numerical value supplied is used as the queue size, 0 meaning
1590 .. _setting-tcp-idle-timeout:
1592 ``tcp-idle-timeout``
1593 --------------------
1598 Maximum time in seconds that a TCP DNS connection is allowed to stay
1599 open while being idle, meaning without PowerDNS receiving or sending
1602 .. _setting-traceback-handler:
1604 ``traceback-handler``
1605 ---------------------
1610 Enable the Linux-only traceback handler.
1612 .. _setting-trusted-notification-proxy:
1614 ``trusted-notification-proxy``
1615 ------------------------------
1619 IP address of incoming notification proxy
1621 .. _setting-udp-truncation-threshold:
1623 ``udp-truncation-threshold``
1624 ----------------------------
1625 .. versionchanged:: 4.2.0
1626 Before 4.2.0, the default was 1680
1631 EDNS0 allows for large UDP response datagrams, which can potentially
1632 raise performance. Large responses however also have downsides in terms
1633 of reflection attacks. Maximum value is 65535, but values above
1634 4096 should probably not be attempted.
1638 1232 is the largest number of payload bytes that can fit in the smallest IPv6 packet.
1639 IPv6 has a minimum MTU of 1280 bytes (:rfc:`RFC 8200, section 5 <8200#section-5>`), minus 40 bytes for the IPv6 header, minus 8 bytes for the UDP header gives 1232, the maximum payload size for the DNS response.
1641 .. _setting-version-string:
1646 - Any of: ``anonymous``, ``powerdns``, ``full``, String
1649 When queried for its version over DNS
1650 (``dig chaos txt version.bind @pdns.ip.address``), PowerDNS normally
1651 responds truthfully. With this setting you can overrule what will be
1652 returned. Set the ``version-string`` to ``full`` to get the default
1653 behaviour, to ``powerdns`` to just make it state
1654 ``Served by PowerDNS - https://www.powerdns.com/``. The ``anonymous``
1655 setting will return a ServFail, much like Microsoft nameservers do. You
1656 can set this response to a custom value as well.
1658 .. _setting-webserver:
1666 Start a webserver for monitoring. See :doc:`performance`".
1668 .. versionchanged:: 4.1.0
1669 It was necessary to enable the webserver to use the REST API, this is no longer the case.
1671 .. _setting-webserver-address:
1673 ``webserver-address``
1674 ---------------------
1677 - Default: 127.0.0.1
1679 IP Address for webserver/API to listen on.
1681 .. _setting-webserver-allow-from:
1683 ``webserver-allow-from``
1684 ------------------------
1686 - IP ranges, separated by commas or whitespace
1687 - Default: 127.0.0.1,::1
1689 .. versionchanged:: 4.1.0
1691 Default is now 127.0.0.1,::1, was 0.0.0.0/0,::/0 before.
1693 Webserver/API access is only allowed from these subnets.
1695 .. _setting-webserver-loglevel:
1697 ``webserver-loglevel``
1698 ----------------------
1699 .. versionadded:: 4.2.0
1701 - String, one of "none", "normal", "detailed"
1703 The amount of logging the webserver must do. "none" means no useful webserver information will be logged.
1704 When set to "normal", the webserver will log a line per request that should be familiar::
1706 [webserver] e235780e-a5cf-415e-9326-9d33383e739e 127.0.0.1:55376 "GET /api/v1/servers/localhost/bla HTTP/1.1" 404 196
1708 When set to "detailed", all information about the request and response are logged::
1710 [webserver] e235780e-a5cf-415e-9326-9d33383e739e Request Details:
1711 [webserver] e235780e-a5cf-415e-9326-9d33383e739e Headers:
1712 [webserver] e235780e-a5cf-415e-9326-9d33383e739e accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
1713 [webserver] e235780e-a5cf-415e-9326-9d33383e739e accept-encoding: gzip, deflate
1714 [webserver] e235780e-a5cf-415e-9326-9d33383e739e accept-language: en-US,en;q=0.5
1715 [webserver] e235780e-a5cf-415e-9326-9d33383e739e connection: keep-alive
1716 [webserver] e235780e-a5cf-415e-9326-9d33383e739e dnt: 1
1717 [webserver] e235780e-a5cf-415e-9326-9d33383e739e host: 127.0.0.1:8081
1718 [webserver] e235780e-a5cf-415e-9326-9d33383e739e upgrade-insecure-requests: 1
1719 [webserver] e235780e-a5cf-415e-9326-9d33383e739e user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0
1720 [webserver] e235780e-a5cf-415e-9326-9d33383e739e No body
1721 [webserver] e235780e-a5cf-415e-9326-9d33383e739e Response details:
1722 [webserver] e235780e-a5cf-415e-9326-9d33383e739e Headers:
1723 [webserver] e235780e-a5cf-415e-9326-9d33383e739e Connection: close
1724 [webserver] e235780e-a5cf-415e-9326-9d33383e739e Content-Length: 49
1725 [webserver] e235780e-a5cf-415e-9326-9d33383e739e Content-Type: text/html; charset=utf-8
1726 [webserver] e235780e-a5cf-415e-9326-9d33383e739e Server: PowerDNS/0.0.15896.0.gaba8bab3ab
1727 [webserver] e235780e-a5cf-415e-9326-9d33383e739e Full body:
1728 [webserver] e235780e-a5cf-415e-9326-9d33383e739e <!html><title>Not Found</title><h1>Not Found</h1>
1729 [webserver] e235780e-a5cf-415e-9326-9d33383e739e 127.0.0.1:55376 "GET /api/v1/servers/localhost/bla HTTP/1.1" 404 196
1731 The value between the hooks is a UUID that is generated for each request. This can be used to find all lines related to a single request.
1734 The webserver logs these line on the NOTICE level. The :ref:`setting-loglevel` seting must be 5 or higher for these lines to end up in the log.
1736 .. _setting-webserver-max-bodysize:
1738 ``webserver-max-bodysize``
1739 --------------------------
1740 .. versionadded:: 4.2.0
1745 Maximum request/response body size in megabytes.
1747 .. _setting-webserver-password:
1749 ``webserver-password``
1750 ----------------------
1754 The plaintext password required for accessing the webserver.
1756 .. _setting-webserver-port:
1764 The port where webserver/API will listen on.
1766 .. _setting-webserver-print-arguments:
1768 ``webserver-print-arguments``
1769 -----------------------------
1774 If the webserver should print arguments.
1776 .. _setting-write-pid:
1784 If a PID file should be written.
1786 .. _setting-xfr-max-received-mbytes:
1788 ``xfr-max-received-mbytes``
1789 ---------------------------
1794 Specifies the maximum number of received megabytes allowed on an
1795 incoming AXFR/IXFR update, to prevent resource exhaustion. A value of 0
1796 means no restriction.