when the SOA record for a domain is disabled, the entire domain is
considered to be disabled.
-This value cannot be set with :doc:`pdnsutil <pdnsutil>`.
+This value cannot be set with :doc:`pdnsutil <../manpages/pdnsutil.1>`.
Effects: the record (or domain, respectively) will not be visible to DNS
clients. The REST API will still see the record (or domain). Even if a
Specifies the full path of a directory that will contain DNSSEC keys.
This option enables DNSSEC on the backend. Keys can be created/managed
-with :doc:`pdnsutil <pdnsutil>`, and the backend stores these keys in files with key
+with :doc:`pdnsutil <../manpages/pdnsutil.1>`, and the backend stores these keys in files with key
flags and active/disabled state encoded in the key filenames.
Zonefile format
- Experimental support for ed25519 DNSSEC signatures (when compiled
with libsodium support).
- IXFR consumption support.
-- Many new :doc:`pdnsutil <pdnsutil>` commands
+- Many new :doc:`pdnsutil <../manpages/pdnsutil.1>` commands
- ``help`` command now produces the help
- Warns if the configuration file cannot be read
Important changes:
-- ``pdnssec`` has been renamed to :doc:`pdnsutil <pdnsutil>`
+- ``pdnssec`` has been renamed to :doc:`pdnsutil <../manpages/pdnsutil.1>`
- PowerDNS Authoritative Server now listens by default on all IPv6
addresses.
- The default for ``pdnsutil secure-zone`` has been changed from 1 2048
This is the second release in the 4.1 train.
- This is a bug-fix only release, with fixes to the LDAP and MySQL backends, the :doc:`pdnsutil <pdnsutil>` tool, and PDNS internals.
+ This is a bug-fix only release, with fixes to the LDAP and MySQL backends, the :doc:`pdnsutil <../manpages/pdnsutil.1>` tool, and PDNS internals.
Changes since 4.1.1:
This is the third release candidate of the PowerDNS Authoritative Server in the 4.1 release train.
This release features various bug fixes and some improvements to
- :doc:`pdnsutil <pdnsutil>`.
+ :doc:`pdnsutil <../manpages/pdnsutil.1>`.
.. change::
:tags: Bug Fixes
:pullreq: 5883
:tickets: 5853
- Add ``add-meta`` command to :doc:`pdnsutil <pdnsutil>` that can be used to append
+ Add ``add-meta`` command to :doc:`pdnsutil <../manpages/pdnsutil.1>` that can be used to append
to existing metadata without clobbering it.
.. change::
* lmdbbackend databases now get a UUID assigned, making it easy for external software to spot if a database was completely replaced
* lmdbbackend databases now optionally use random IDs for objects
* a new LUA function called ``ifurlextup``, and improvements in other LUA record functions
- * autoprimary management in :doc:`pdnsutil <pdnsutil>` and the HTTP API
+ * autoprimary management in :doc:`pdnsutil <../manpages/pdnsutil.1>` and the HTTP API
* in beta, a key roller daemon, currently not packaged
Please make sure to read the :doc:`upgrade notes <../upgrading>` before upgrading.
* lmdbbackend databases now get a UUID assigned, making it easy for external software to spot if a database was completely replaced
* lmdbbackend databases now optionally use random IDs for objects
* a new LUA function called ``ifurlextup``, and improvements in other LUA record functions
- * autoprimary management in :doc:`pdnsutil <pdnsutil>` and the HTTP API
+ * autoprimary management in :doc:`pdnsutil <../manpages/pdnsutil.1>` and the HTTP API
* in beta, a key roller daemon, currently not packaged
Please make sure to read the :doc:`upgrade notes <../upgrading>` before upgrading.
* lmdbbackend databases now get a UUID assigned, making it easy for external software to spot if a database was completely replaced
* lmdbbackend databases now optionally use random IDs for objects
* a new LUA function called ``ifurlextup``, and improvements in other LUA record functions
- * autoprimary management in :doc:`pdnsutil <pdnsutil>` and the HTTP API
+ * autoprimary management in :doc:`pdnsutil <../manpages/pdnsutil.1>` and the HTTP API
Please make sure to read the :doc:`upgrade notes <../upgrading>` before upgrading.
* lmdbbackend databases now get a UUID assigned, making it easy for external software to spot if a database was completely replaced
* lmdbbackend databases now optionally use random IDs for objects
* a new LUA function called ``ifurlextup``
- * autoprimary management in :doc:`pdnsutil <pdnsutil>` and the HTTP API
+ * autoprimary management in :doc:`pdnsutil <../manpages/pdnsutil.1>` and the HTTP API
Please make sure to read the :doc:`upgrade notes <../upgrading>` before upgrading.
This should be done as the ``pdns`` user (or root), as sqlite3 requires write access to the directory of the database file.
.. note::
- :doc:`pdnsutil <pdnsutil>` is a tool that can manipulate zones, set DNSSEC parameters for zones and does :doc:`many other <../manpages/pdnsutil.1>` things.
- It is *highly* recommended to use :doc:`pdnsutil <pdnsutil>` or the :doc:`HTTP API <../http-api/index>` to modify zones instead of using raw SQL,
- as :doc:`pdnsutil <pdnsutil>` and the API perform checks on the data and post-store changes to prevent issues when serving DNS data.
+ :doc:`pdnsutil <../manpages/pdnsutil.1>` is a tool that can manipulate zones, set DNSSEC parameters for zones and does many other things.
+ It is *highly* recommended to use :doc:`pdnsutil <../manpages/pdnsutil.1>` or the :doc:`HTTP API <../http-api/index>` to modify zones instead of using raw SQL,
+ as :doc:`pdnsutil <../manpages/pdnsutil.1>` and the API perform checks on the data and post-store changes to prevent issues when serving DNS data.
If we now requery our database, ``www.example.com`` should be present::
``pdnsutil``
~~~~~~~~~~~~
-To perform zone and record changes using inbuilt tools, the :doc:`pdnsutil <pdnsutil>` command can be used. All available options are described in the online :doc:`manual page <../manpages/pdnsutil.1>` as well as in ``man pdnsutil``.
+To perform zone and record changes using inbuilt tools, the ``pdnsutil`` command can be used. All available options are described in the online :doc:`manual page <manpages/pdnsutil.1>` as well as in ``man pdnsutil``.
Running in the foreground
-------------------------
pdnsutil behaviour changes
^^^^^^^^^^^^^^^^^^^^^^^^^^
-A few changes of behaviour have been implemented in :doc:`pdnsutil <pdnsutil>`.
+A few changes of behaviour have been implemented in :doc:`pdnsutil <manpages/pdnsutil.1>`.
* The ``add-zone-key`` command used to default to creating a ZSK,
if no key type was given. This default has changed to KSK.