> * Going through upstream changes on a commit-by-commit basis alongside the
> release notes, I found one
> commit which may include backward-incompatible changes for some users -
> https://gitlab.isc.org/isc-
> projects/bind9/-/commit/adf104a06339f101d295c1c7980725be5af73dfa
> It includes the following note - "Instances of this record will need the
> placeholder period added to them
> when upgrading."
Thanks for flagging. I can't reach gitlab at the moment ("connection
refused"), but I saw this in the release notes[1] as well. Essentially
it's making bind9 conform to the RFC for that particular record:
"""
AMTRELAY type 0 presentation format handling was wrong.
RFC 8777 specifies a placeholder value of . for the gateway field when
the gateway type is 0 (no gateway). This was not being checked for, nor
was it emitted when displaying the record. This has been corrected.
Instances of this record will need the placeholder period added to them when
upgrading. [GL #5639]
"""
I have never heard of this AMTRELAY record before, and can't say how
common its usage is, or even how common the *incorrect* usage is.
What happens if the bad record is in the DB, and bind is upgraded? Does it
refuse to start?
1. https://bind9.readthedocs.io/en/stable/notes.html#notes-for-
bind-9-20-17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2126464
Title:
Backport of bind9 for questing, noble, and jammy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind-dyndb-ldap/+bug/2126464/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
