unitialized
unixodbc
unixtime
+unparsable
unparseable
UNPRIV
unpublishdomainkey
- ``simple``: Search the requested domain by comparing the
associatedDomain attributes with the domain string in the question.
-- ``tree``: Search entires by translating the domain string into a LDAP
+- ``tree``: Search entries by translating the domain string into a LDAP
dn. Your LDAP tree must be designed in the same way as the DNS LDAP
tree. The question for "myhost.linuxnetworks.de" would translate into
"dc=myhost,dc=linuxnetworks,dc=de,ou=hosts=..." and the entry where
:pullreq: 6555
:tickets: 6396
- Report unparseable data in stoul invalid_argument exception
+ Report unparsable data in stoul invalid_argument exception
.. change::
:tags: Improvements
:tags: Bug Fixes
:pullreq: 6396
- Report unparseable data in stoul ``invalid_argument`` exception.
+ Report unparsable data in stoul ``invalid_argument`` exception.
.. change::
:tags: New Features, Tools
parameters for pdnssec.
- `commit 2f2b014 <https://github.com/PowerDNS/pdns/commit/2f2b014>`__:
apply variant of code in `ticket
- 714 <https://github.com/PowerDNS/pdns/issues/714>`__ so we can lauch
+ 714 <https://github.com/PowerDNS/pdns/issues/714>`__ so we can launch
pipe backend scripts with parameters, plus add experimental code that
if pipe-command is a unix domain socket, we use that.
- `commit 9566683 <https://github.com/PowerDNS/pdns/commit/9566683>`__:
fact only made things worse.
- LDAP backend updates from its author Norbert Sendetzky. Reverse
lookups should work now too.
-- An error message about unparseable packets did not include the
+- An error message about unparsable packets did not include the
originating IP address (fixed by Mark Bergsma)
- PowerDNS can now be started via path resolution while running with a
guardian. Suggested by Maurice Nonnekes.
``/etc`` and ``/home``, possibly being unable to write AXFR'd zones.
PowerDNS also reacts to notifies by immediately checking if the zone has
-updated and if so, retransfering it.
+updated and if so, retransferring it.
All backends which implement this feature must make sure that they can
handle transactions so as to not leave the zone in a half updated state.
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.
.. note::
- 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.
+ The webserver logs these line on the NOTICE level. The :ref:`setting-loglevel` setting must be 5 or higher for these lines to end up in the log.
.. _setting-webserver-max-bodysize:
proxy-protocol-from=192.0.2.2
-For more informations, see the `authoritative server's documentation <https://doc.powerdns.com/authoritative/settings.html#proxy-protocol-from>`_ or the `recursor's documentation <https://docs.powerdns.com/recursor/settings.html#proxy-protocol-from>`_.
+For more information, see the `authoritative server's documentation <https://doc.powerdns.com/authoritative/settings.html#proxy-protocol-from>`_ or the `recursor's documentation <https://docs.powerdns.com/recursor/settings.html#proxy-protocol-from>`_.
From clients to dnsdist
^^^^^^^^^^^^^^^^^^^^^^^
Note that this require ``SO_REUSEPORT`` support in the underlying operating system (added for example in Linux 3.9).
Please also be aware that doing so will increase lock contention and might not therefore scale linearly, as discussed below.
-Another possibility is to use the reuseport option to run several dnsdist processes in parallel on the same host, thus avoiding the lock contention issue at the cost of having to deal with the fact that the different processes will not share informations, like statistics or DDoS offenders.
+Another possibility is to use the reuseport option to run several dnsdist processes in parallel on the same host, thus avoiding the lock contention issue at the cost of having to deal with the fact that the different processes will not share information, like statistics or DDoS offenders.
The UDP threads handling the responses from the backends do not use a lot of CPU, but if needed it is also possible to add the same backend several times to the dnsdist configuration to distribute the load over several responder threads::
:tags: Improvements
:pullreq: 6637
- Don't copy unitialized values of SuffixMatchTree
+ Don't copy uninitialized values of SuffixMatchTree
.. change::
:tags: Improvements
:param int clientIPMask: The network mask to apply to the address. Default is 32 for IPv4, 128 for IPv6.
:param int clientIPPortMask: The port mask to use to specify a range of ports to match, when the clients are behind a CG-NAT.
- Please see the documentation for :func:`setDynBlocksAction` to confirm which actions are supported by the action paramater.
+ Please see the documentation for :func:`setDynBlocksAction` to confirm which actions are supported by the action parameter.
.. function:: addDynBlocks(addresses, message[, seconds=10[, action]])
:param int seconds: The number of seconds this block to expire
:param int action: The action to take when the dynamic block matches, see :ref:`DNSAction <DNSAction>`. (default to DNSAction.None, meaning the one set with :func:`setDynBlocksAction` is used)
- Please see the documentation for :func:`setDynBlocksAction` to confirm which actions are supported by the action paramater.
+ Please see the documentation for :func:`setDynBlocksAction` to confirm which actions are supported by the action parameter.
.. function:: clearDynBlocks()
:pullreq: 8047
:tickets: 8008
- Another time sensistive test fixed with a fixednow construct.
+ Another time sensitive test fixed with a fixednow construct.
.. change::
:tags: New Features
:pullreq: 14222
:tickets: 14185
- Report error and adjust max-mthreads when linux map limit (vm.max_map_count) is too low to accomodate resource usage under load.
+ Report error and adjust max-mthreads when linux map limit (vm.max_map_count) is too low to accommodate resource usage under load.
.. changelog::
:version: 5.0.5
Cache Management
----------------
-Sometimes a domain fails to resolve due to an error on the domain owner's end, or records for your own domain have updated and you want your users to immediatly see them without waiting for the TTL to expire.
+Sometimes a domain fails to resolve due to an error on the domain owner's end, or records for your own domain have updated and you want your users to immediately see them without waiting for the TTL to expire.
The :doc:`rec_control <manpages/rec_control.1>` tool can be used to selectively wipe the cache.
To wipe all records for the exact name 'www.example.com'::
Release 5.0.0 will install a default old-style ``recursor.conf`` file.
- Starting with version 5.1.0, in the absense of a ``recursor.yml`` file, an existing ``recursor.conf`` will be processed as YAML,
+ Starting with version 5.1.0, in the absence of a ``recursor.yml`` file, an existing ``recursor.conf`` will be processed as YAML,
if that fails, it will be processed as old-style configuration.
Packages will stop installing a old-style ``recursor.conf`` file and start installing a default ``recursor.conf`` file containing YAML syntax.
- With the release of 5.2.0, the default will be to expect a YAML configuation file and reading of old-style ``recursor.conf`` files will have to be enabled specifically by providing a command line option.
+ With the release of 5.2.0, the default will be to expect a YAML configuration file and reading of old-style ``recursor.conf`` files will have to be enabled specifically by providing a command line option.
In a future release support for the "old-style" ``recursor.conf`` settings file will be dropped.
Subnets can also be prefixed with a ``!``, specifying negation.
This can be used to deny addresses from a previously allowed range.
-For example, ``alow-from`` takes a sequence of subnets:
+For example, ``allow-from`` takes a sequence of subnets:
.. code-block:: yaml
tsig:
name: name of key
algo: algorithm
- secret: Base64 endcoded secret
+ secret: Base64 encoded secret
refreshPeriod: 86400
retryOnErrorPeriod: 60
maxReceivedMBytes: 0 Zero mean no restrcition
AllowedAdditionalQType
^^^^^^^^^^^^^^^^^^^^^^
-As of version 5.1.0, an allowed addtional qtype entry is defined as:
+As of version 5.1.0, an allowed additional qtype entry is defined as:
.. code-block:: yaml
.. note::
Starting with version 5.0.0, :program:`Recursor` supports a new YAML syntax for configuration files.
A configuration using the old style syntax can be converted to a YAML configuration using the instructions in :doc:`appendices/yamlconversion`.
- In a future release support for the "old-style" settings decribed here will be dropped.
+ In a future release support for the "old-style" settings described here will be dropped.
See :doc:`yamlsettings` for details.
.. note::
projects / thirdparty / pdns.git / commitdiff
