Loop version 1.99.10 is available

Loop version 1.99.10 is available

March 3, 2026

Loop version 1.99.10 has been released (tagged at 1.99.10.20260302081434.1cfd6e70ac). This is in a series of releases made from the 1.99 development branch.

The following are release notes for Loop 1.99.10:

  • RT1826: Limit NSEC3 iterations per RFC 9276. The max-sec3-iterations named.conf(5) option was added to configure the limit, and it defaults to 10. dnssec-signzone(1) warns if a non-zero NSEC3 additional iterations value or a non-zero length NSEC3 salt is used when signing a zone.
  • RT1831: Return EDE option when queries fail due to recursive clients going over quota. The Over Quota (32) INFO-CODE in the EDNS Extended DNS Errors option is returned.
  • RT1827: Return EDE option when responses are truncated due to RRL. The Rate Limited (31) INFO-CODE in the EDNS Extended DNS Errors option is returned.
  • RT1820: Fix check for max-rsa-exponent-size option
  • RT1825: Add RFC notes section to the Loop user manual
  • RT1811: Remove unnecessary assignment that causes Sphinx warning
  • RT1709: Add RPZ intent config clause with values blocking/censoring/filtering; the Blocked (15), Censored (16), and Filtered (17) INFO-CODEs in the EDNS Extended DNS Errors option are returned depending on the configured intent of the RPZ zone.
  • RT1820: Limit max RSA public exponent bits size to a default of 64; values up to 256 are allowed.
  • RT1820: Further limit RSA public exponent to 64 bits
  • RT1720: Return EDE option for SERVFAIL if a zone is not ready to be queried. The Not Ready (14) INFO-CODE is returned if the zone data has not been loaded. The Invalid Data (24) INFO-CODE Is returned if the zone data is stale or missing.
  • RT1819: Fix Debian package homepage URLs
  • RT1780: Return the Not Authoritative (20) INFO-CODE in the EDNS Extended DNS Errors option when the server is not authoritative for the zone

Some more development releases will be made from this branch until Loop 2.0 is ready to be branched. You can read about Loop branches and version numbering.

We wanted to merge a couple of large branches into this release, but there was insufficient time. We will likely break them up and merge them phase by phase in future releases.

Loop Posts RSS