Make configure call PDNS_CHECK_LIBCURL when needed

[thirdparty/pdns.git] / docs / upgrading.rst

diff --git a/docs/upgrading.rst b/docs/upgrading.rst
index 3d979d5b8c79a4a49b5aefdd277a9f54257d4a48..622d1087d14358e7738bad550550a8b7386c8c5e 100644 (file)
--- a/docs/upgrading.rst
+++ b/docs/upgrading.rst
@@ -8,11 +8,27 @@ Please upgrade to the PowerDNS Authoritative Server 4.0.0 from 3.4.2+.
 See the `3.X <https://doc.powerdns.com/3/authoritative/upgrading/>`__
 upgrade notes if your version is older than 3.4.2.
 
+4.1.X to 4.2.0
+--------------
+
+- Superslave operation is no longer enabled by default, use :ref:`setting-superslave` to enable. This setting was called ``supermaster`` in some 4.2.0 prereleases.
+- The gsqlite3 backend, and the DNSSEC database for the BIND backend, have a new journal-mode setting. This setting defaults to `WAL <https://www.sqlite.org/wal.html>`_; older versions of PowerDNS did not set the journal mode, which means they used the SQLite default of DELETE.
+
+4.1.0 to 4.1.1
+--------------
+
+- The :doc:`Generic MySQL backend <backends/generic-mysql>` schema has
+  changed: the ``notified_serial`` column default in the ``domains``
+  table has been changed from ``INT DEFAULT NULL`` to ``INT UNSIGNED
+  DEFAULT NULL``:
+
+  - ``ALTER TABLE domains MODIFY notified_serial INT UNSIGNED DEFAULT NULL;``
+
 4.0.X to 4.1.0
 --------------
 
 - Recursion has been removed, see the :doc:`dedicated migration guide <guides/recursion>`.
-- ALIAS record expension is disabled by default, use :ref:`setting-expand-alias` to enable.
+- ALIAS record expansion is disabled by default, use :ref:`setting-expand-alias` to enable.
 - *Your LDAP schema might need to be updated*, because new record types
   have been added (see below) and the ``dNSDomain2`` type has been
   changed.
@@ -60,7 +76,7 @@ and ``--with-pgsql-config`` ``configure`` options have been deprecated.
 ``--with-pg-config`` to specify a path to a non-default ``pg_config`` if
 you have Postgresql installed in a non-default location.
 
-The ``--enable-libsodium`` configure flag has changed from 'no' to 'auto'.
+The ``--with-libsodium`` configure flag has changed from 'no' to 'auto'.
 This means that if libsodium and its development header are installed, it will be linked in.
 
 The improved :doc:`LDAP Backend <backends/ldap>` backend now requires Kerberos headers to be installed.