@Manus: Definitively not!
Moving of the binaries happened through the newly installed bind9 package, and
all my configuration issues could be solved by following the advices in the
bind9 configurations. I had to set some new options and change the value of
other options, where now certain precon
The most important question for me is still: Why does such a version jump occur
during the last months of a LTS version?
In a parallel installed debian 11, I am still on bind 9.16, this received the
last patch from the isc-bind team-member Ondřej Surý at Thu, 25 Jul 2024
21:51:33 +
See:
htt
100% agreement, that such an installation verification is needed.
#2075542 the bad upgrade from (1:9.18.28-0ubuntu0.20.04.1) over
(1:9.16.48-0ubuntu0.20.04.1)
killed my dns server, because of many config errors.
I really would expect, that such a test is performed for every mission
critical appl
** Summary changed:
- bind9 1:9.18.28-0ubuntu0.20.04.1 brakes local system
+ bind9 1:9.18.28-0ubuntu0.20.04.1 breakes local system
** Description changed:
Using ubuntu 20.04 LTS
5.4.0-190-generic #210-Ubuntu SMP Fri Jul 5 17:03:38 UTC 2024 x86_64 x86_64
x86_64 GNU/Linux
- I installed today
Public bug reported:
Using ubuntu 20.04 LTS
5.4.0-190-generic #210-Ubuntu SMP Fri Jul 5 17:03:38 UTC 2024 x86_64 x86_64
x86_64 GNU/Linux
I installed today an update for bind9
(1:9.18.28-0ubuntu0.20.04.1) over (1:9.16.48-0ubuntu0.20.04.1)
which killed my existing configuration.
The following bin
