All these ``log_facilities`` is available:
- * ``log_all``
- * ``log_ntlog``
- * ``log_alert``
- * ``log_critical``
- * ``log_error``
- * ``log_warning``
- * ``log_notice,``
- * ``log_info``
- * ``log_debug``
- * ``log_none``
+* ``log_all``
+* ``log_ntlog``
+* ``log_alert``
+* ``log_critical``
+* ``log_error``
+* ``log_warning``
+* ``log_notice,``
+* ``log_info``
+* ``log_debug``
+* ``log_none``
``dnspacket()``
~~~~~~~~~~~~~~~
always return something, if there are no values, you shall return empty
set or false.
- * Mandatory: No
- * Parameters: name
- * Reply: hash of key to array of strings
+* Mandatory: No
+* Parameters: name
+* Reply: hash of key to array of strings
Example JSON/RPC
''''''''''''''''
:tags: Tools, Improvements
:pullreq: 4584
- Allow setting the account of a zone via pdnsutil (Tuxis Internet Engineering).
+ Allow setting the account of a zone via pdnsutil (Tuxis Internet Engineering).
.. change::
:tags: Internals, New Features
Disclosure Policy
^^^^^^^^^^^^^^^^^
- - Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.
- - Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
- - We will always credit researchers in our :doc:`../security-advisories/index`.
-
+- Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.
+- Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
+- We will always credit researchers in our :doc:`../security-advisories/index`.
Getting Started
---------------
- * :doc:`Install the Authoritative Server <installation>`
- * :doc:`Configure the Server <settings>`
- * :doc:`Configure the backend(s) <backends/index>`
+* :doc:`Install the Authoritative Server <installation>`
+* :doc:`Configure the Server <settings>`
+* :doc:`Configure the backend(s) <backends/index>`
Getting Support
---------------
Public support is available via several different channels:
- * This documentation
- * `The mailing list <https://www.powerdns.com/mailing-lists.html>`_
- * ``#powerdns`` on `irc.oftc.net <irc://irc.oftc.net/#powerdns>`_
+* This documentation
+* `The mailing list <https://www.powerdns.com/mailing-lists.html>`_
+* ``#powerdns`` on `irc.oftc.net <irc://irc.oftc.net/#powerdns>`_
The PowerDNS company can provide help or support you in private as well.
For first class and rapid support, please contact powerdns.support@powerdns.com, or see the `.com website <https://www.powerdns.com/support-services-consulting.html>`__.
**Formatting options:**
- - ``%1%`` to ``%4%`` are individual octets
- - Example record query: ``1.0.0.127.in-addr.arpa``
- - ``%1%`` = 127
- - ``%2%`` = 0
- - ``%3%`` = 0
- - ``%4%`` = 1
- - ``%5%`` joins the four decimal octets together with dashes
- - Example: ``%5%.static.example.com`` is equivalent to ``%1%-%2%-%3%-%4%.static.example.com``
- - ``%6%`` converts each octet from decimal to hexadecimal and joins them together
- - Example: A query for ``15.0.0.127.in-addr.arpa``
- - ``%6`` would be ``7f00000f`` (127 is 7f, and 15 is 0f in hexadecimal)
+ - ``%1%`` to ``%4%`` are individual octets
+ - Example record query: ``1.0.0.127.in-addr.arpa``
+ - ``%1%`` = 127
+ - ``%2%`` = 0
+ - ``%3%`` = 0
+ - ``%4%`` = 1
+ - ``%5%`` joins the four decimal octets together with dashes
+ - Example: ``%5%.static.example.com`` is equivalent to ``%1%-%2%-%3%-%4%.static.example.com``
+ - ``%6%`` converts each octet from decimal to hexadecimal and joins them together
+ - Example: A query for ``15.0.0.127.in-addr.arpa``
+ - ``%6`` would be ``7f00000f`` (127 is 7f, and 15 is 0f in hexadecimal)
**NOTE:** At the current time, only forward dotted format works with :func:`createForward` (i.e. ``127.0.0.1.static.example.com``)
Formatting options:
- - ``%1%`` to ``%32%`` are individual characters (nibbles)
- - **Example PTR record query:** ``a.0.0.0.1.0.0.2.ip6.arpa``
- - ``%1%`` = 2
- - ``%2%`` = 0
- - ``%3%`` = 0
- - ``%4%`` = 1
- - ``%33%`` converts the compressed address format into a dashed format, e.g. ``2001:a::1`` to ``2001-a--1``
- - ``%34%`` to ``%41%`` represent the 8 uncompressed 2-byte chunks
- - **Example:** PTR query for ``2001:a:b::123``
- - ``%34%`` - returns ``2001`` (chunk 1)
- - ``%35%`` - returns ``000a`` (chunk 2)
- - ``%41%`` - returns ``0123`` (chunk 8)
+ - ``%1%`` to ``%32%`` are individual characters (nibbles)
+ - **Example PTR record query:** ``a.0.0.0.1.0.0.2.ip6.arpa``
+ - ``%1%`` = 2
+ - ``%2%`` = 0
+ - ``%3%`` = 0
+ - ``%4%`` = 1
+ - ``%33%`` converts the compressed address format into a dashed format, e.g. ``2001:a::1`` to ``2001-a--1``
+ - ``%34%`` to ``%41%`` represent the 8 uncompressed 2-byte chunks
+ - **Example:** PTR query for ``2001:a:b::123``
+ - ``%34%`` - returns ``2001`` (chunk 1)
+ - ``%35%`` - returns ``000a`` (chunk 2)
+ - ``%41%`` - returns ``0123`` (chunk 8)
**NOTE:** At the current time, only dashed compressed format works for this function (i.e. ``2001-a-b--1.static6.example.com``)
Reference
---------
- .. toctree::
+.. toctree::
:maxdepth: 2
functions
We provide a convenient object class that can store unique ComboAddresses in no particular
order and allows fast retrieval of individual elements based on their values
- .. code-block:: lua
-
- addr = newCA("1.2.3.4")
- myset = newCAS()
- myset:add(addr)
- if myset:check(addr) then -- prints "found!"
- print('found!')
- end
+.. code-block:: lua
+
+ addr = newCA("1.2.3.4")
+ myset = newCAS()
+ myset:add(addr)
+ if myset:check(addr) then -- prints "found!"
+ print('found!')
+ end
Functions and methods of a ``ComboAddressSet``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
LUA Reference
-------------
- .. toctree::
+.. toctree::
:maxdepth: 2
comboaddress
:param string message: The message to log
:param int loglevel: The urgency level of the message. Defaults to `pdns.loglevels.Warning`
- You can use the following constants as log levels :
-
- - `pdns.loglevels.Alert`
- - `pdns.loglevels.Critical`
- - `pdns.loglevels.Debug`
- - `pdns.loglevels.Emergency`
- - `pdns.loglevels.Info`
- - `pdns.loglevels.Notice`
- - `pdns.loglevels.Warning`
- - `pdns.loglevels.Error`
+ You can use the following constants as log levels :
+
+ - `pdns.loglevels.Alert`
+ - `pdns.loglevels.Critical`
+ - `pdns.loglevels.Debug`
+ - `pdns.loglevels.Emergency`
+ - `pdns.loglevels.Info`
+ - `pdns.loglevels.Notice`
+ - `pdns.loglevels.Warning`
+ - `pdns.loglevels.Error`
.. function:: pdnsrandom([maximum])
Before a supermaster notification succeeds, the following conditions
must be met:
- - :ref:`setting-supermaster` support must be enabled
- - The supermaster must carry a SOA record for the notified domain
- - The supermaster IP must be present in the 'supermaster' table
- - The set of NS records for the domain, as retrieved by the slave from the supermaster, must include the name that goes with the IP address in the supermaster table
- - If your master sends signed NOTIFY it will mark that TSIG key as the TSIG key used for retrieval as well
- - If you turn off :ref:`setting-allow-unsigned-supermaster`, then your supermaster(s) are required to sign their notifications.
+- :ref:`setting-supermaster` support must be enabled
+- The supermaster must carry a SOA record for the notified domain
+- The supermaster IP must be present in the 'supermaster' table
+- The set of NS records for the domain, as retrieved by the slave from the supermaster, must include the name that goes with the IP address in the supermaster table
+- If your master sends signed NOTIFY it will mark that TSIG key as the TSIG key used for retrieval as well
+- If you turn off :ref:`setting-allow-unsigned-supermaster`, then your supermaster(s) are required to sign their notifications.
.. warning::
If you use another PowerDNS server as master and have
- ``mrtg``: Dump statistics in mrtg format. See the performance
:ref:`counters` documentation.
- .. note::
+.. note::
Packages provided by Operating System vendors might support
different or less commands.