Changelogs for 4.3.x
====================
+.. changelog::
+ :version: 4.3.2
+ :released: 12th of March 2021
+
+ This is version 4.3.2 of the Authoritative Server.
+ This release fixes latency calculations to match the approach used in 4.4.0, to make comparisons between 4.3 and 4.4 more useful.
+ It also contains a few build-related improvements.
+
+ .. change::
+ :tags: Bug Fixes
+ :pullreq: 9786
+
+ fix rounding inaccuracy in latency statistics (Kees Monshouwer)
+
.. changelog::
:version: 4.3.1
:released: 22nd of September 2020
-@ 86400 IN SOA pdns-public-ns1.powerdns.com. pieter\.lexis.powerdns.com. 2021030901 10800 3600 604800 10800
+@ 86400 IN SOA pdns-public-ns1.powerdns.com. pieter\.lexis.powerdns.com. 2021031201 10800 3600 604800 10800
@ 3600 IN NS pdns-public-ns1.powerdns.com.
@ 3600 IN NS pdns-public-ns2.powerdns.com.
auth-4.3.0-rc2.security-status 60 IN TXT "2 Unsupported pre-release (known vulnerabilities)"
auth-4.3.0.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2020-05.html"
auth-4.3.1.security-status 60 IN TXT "1 OK"
+auth-4.3.2.security-status 60 IN TXT "1 OK"
auth-4.4.0-alpha1.security-status 60 IN TXT "2 Unsupported pre-release (no known vulnerabilities)"
auth-4.4.0-alpha2.security-status 60 IN TXT "2 Unsupported pre-release (no known vulnerabilities)"
auth-4.4.0-alpha3.security-status 60 IN TXT "2 Unsupported pre-release (no known vulnerabilities)"
Latency calculation changes
^^^^^^^^^^^^^^^^^^^^^^^^^^^
-It turned out that average latency calculations in earlier versions used integers instead of doubles, which led to the throwing away of any data points between 'the current average' and 1000ms above it, instead of having those data points affecting the average.
-In 4.4.0, we `started using doubles for this <https://github.com/PowerDNS/pdns/pull/9768/files>`__, which means the latency calculation is accurate now.
+It turned out that average latency calculations in earlier versions used integers instead of floating point variables, which led to the throwing away of any data points between 'the current average' and 1000ms above it, instead of having those data points affecting the average.
+In 4.3.2 and 4.4.0, we `started using floating point variables for this <https://github.com/PowerDNS/pdns/pull/9768/files>`__, which means the latency calculation is accurate now.
+Usually, this means you will see higher latency numbers after upgrading.
MySQL character set detection
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SOA autofilling (i.e. allowing incomplete SOAs in the database) and the API set-ptr feature, that both were deprecated in earlier releases, have now been removed.
Please run ``pdnsutil check-all-zones`` to check for incomplete SOAs.
+4.3.1 to 4.3.2
+--------------
+
+Latency calculation changes
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+It turned out that average latency calculations in earlier versions used integers instead of floating point variables, which led to the throwing away of any data points between 'the current average' and 1000ms above it, instead of having those data points affecting the average.
+In 4.3.2 and 4.4.0, we `started using floating point variables for this <https://github.com/PowerDNS/pdns/pull/9786/files>`__, which means the latency calculation is accurate now.
+Usually, this means you will see higher latency numbers after upgrading.
+
+To be very clear, there is no performance difference between 4.3.1 and 4.3.2.
+The only change is in the latency calculation, which was wrong in 4.3.1 and is correct in 4.3.2.
+This fix was backported to 4.3.2 from 4.4.0 so that users can fairly compare the performance of 4.3.2 and 4.4.0.
+
4.3.0 to 4.3.1
--------------