Skip to content

Release 3.0.13

Compatibility

PowerDNS components have been upgraded to the following versions:

Component Version
Authoritative Server 4.9.7
Recursor 5.1.6

Release 3.0.12

Improvements

  • Documented support for the HTTP storage backend in TopN Reporter
  • Added headers configuration option for the HTTP storage backend in TopN Reporter

Compatibility

PowerDNS components have been upgraded to the following versions:

Component Version
dnsdist 1.9.10

Release 3.0.11

Compatibility

PowerDNS components have been upgraded to the following versions:

Component Version
Authoritative Server 4.9.5
dnsdist 1.9.9
Recursor 5.1.4
ZoneControl 1.6.5

Release 3.0.10

Improvements

  • Execution frequency and timeout for Command Source feeds can now be configured via interval and timeout. See the documentation (Command Source Configuration) for more information.
  • Prometheus alert rules deployed via the monitoring Helm Chart have been improved as follows (both are now in line with dnsdist's alert rule):
    • Recursor alert rule to detect new instances and/or restarts of existing instances has been added
    • Authoritative Server alert rule to detect new instances and/or restarts of existing instances has been adjusted to correctly catch both cases

Compatibility

PowerDNS components have been upgraded to the following versions:

Component Version
dstoredist 2.1.2
TopN Reporter 2.1.2

Release 3.0.9

Bug Fixes

  • Fixed an issue preventing Cloud Control agents from shutting down instantly when a shutdown signal is received.

Compatibility

PowerDNS components have been upgraded to the following versions:

Component Version
Authoritative Server 4.9.4
ZoneControl 1.6.4

Release Notes

Release 3.0.8

Bug Fixes

  • Release 3.0.7 inadvertently activated an upcoming feature which was not yet scheduled for release. This is deactivated and will be included in Cloud Control 3.1 as per the original schedule.

Release 3.0.7

Improvements

  • When choosing IPv6 addresses for outbound traffic via additional interfaces assigned via Multus, Cloud Control now ignores EUI-64 addresses added by the cluster's supporting infrastructure to interfaces intended to be IPv4-only.

Release 3.0.6

Improvements

  • Grafana & Prometheus instances managed via the monitoring Helm Chart can now have additional Service objects configured via the additionalServices parameter: See Additional Grafana Services and Additional Prometheus Services for more information.
  • When choosing IPv6 addresses for outbound traffic via additional interfaces assigned via Multus, Cloud Control now prioritizes the IP addresses assigned directly by the CNI over any potential EUI-64 addresses added by the cluster's supporting infrastructure.

Release 3.0.5

Improvements

  • Additional filtering debug options can now be enabled via debugTXT and debugRules. See the documentation (Filter Settings) for more information.
  • When a dnsdist Pod is deployed with additional network interfaces and a target server has a source override to use a non-eth0 interface, Cloud Control will now ensure dnsdist uses the corresponding IP address as the source instead of the interface. This ensures compatibility when Multus is used together with the SBR CNI plugin.

Compatibility

PowerDNS components have been upgraded to the following versions:

Component Version
Filtering components & Feeds 2.9.4

Release 3.0.4

Improvements

  • Default value for dnsdist's wHashedPertubation is now generated based on the name of the corresponding instance set. After upgrading to this release it will no longer be regenerated for every subsequent helm action.

Bug Fixes

  • Pods and Service Accounts will no longer contain an empty imagePullSecrets tag if no image pull secrets are defined/referenced in the Cloud Control configuration.

Release 3.0.3

Improvements

  • Userplane & Controlplane components now support configuring topologySpreadConstraints

Bug Fixes

  • Userplane
    • Authoritative Server: webserver-max-bodysize and webserver-connection-timeout parameters were unintentionally blocked from being configured. These can now be configured.
    • Recursor: A scenario was possible where deploying Recursor would generate errors if no replicas value was specified. Cloud Control now always correctly assigns a default for replicas for Recursor deployments.

Compatibility

PowerDNS components have been upgraded to the following versions:

Component Version
Authoritative Server 4.9.3
dnsdist 1.9.8
Filtering components & Feeds 2.9.2
Recursor 5.1.3

Release 3.0.2

Compatibility

  • Userplane:
    • Recursor: Upgraded to 5.1.2 - This Recursor release includes a mitigation for CVE-2024-25590, documented in the following security advisory: PowerDNS Security Advisory 2024-04

Release 3.0.1

Bug Fixes

  • Userplane
    • Filtering: Prevent a scenario where Cloud Control fails to create Service objects for any vHosts if Service configuration is defined for individual vHosts.

Release 3.0.0

In this major release of Cloud Control several products from the PowerDNS Security & Reporting portfolio are introduced:

  • DNS filtering can now be configured for both dnsdist and Recursor
  • TopN Reporter can be deployed to gain insight into the DNS traffic

Documentation has also been reworked and is now available in HTML, instead of the previous releases' PDF documentation.

Userplane & Controlplane

For manageability and scalability purposes Cloud Control can now be considered to have 3 major components:

  • Userplane: The PowerDNS base products for DNS Loadbalancing, Recursive DNS, Authoritative DNS and accompanying security solutions
  • Controlplane (new): PowerDNS products for reporting and provisioning of feeds for Userplane security solutions
  • Monitoring: A comprehensive monitoring blueprint which can be deployed alongside Userplane and Controlplane deployments

Future releases of Cloud Control will see more of our security and management products added, mainly to the Controlplane.

Compatibility

PowerDNS components have been upgraded to the following versions:

Component Version
Authoritative Server 4.9.1
dnsdist 1.9.6
dstoredist 2.1.1
Filtering components & Feeds 2.9.0
Lightning Stream 0.4.3
Recursor 5.1.1
TopN Reporter 2.1.1
ZoneControl 1.6.3

Upgrade Notes

Cloud Control 3.0.0 is fully backwards compatible with prior Cloud Control releases.

Some of the container images used by the new Security features are hosted in a separate repository on the OX registry, to which the Cloud Control 2.X registry users do not have access. If you are a Cloud Control 2.X user looking to upgrade to Cloud Control 3.0 and make use of the new Security features, please reach out to your support contact to have a compatible registry user created.