</span></div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">We have tried force transfers, purging journal files and nothing seems to work.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">We rolled back the update to one performed earlier in the month and now everything is working.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Anybody have any idea what is going on with this latest update?</
<div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Thanks,</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Brian<br></div></div></body></html>
We just ran the latest updates for Debian Buster on one of our DNS
servers running bind9 and one of the slave domains is failing with this message:
Aug 2 07:05:20 <hostname> named[76759]: transfer of '<domain name>/IN'
from <ip address>#53: Transfer status: too many records
There are about 1,400 records in that domain which has never posed a
problem in the past.
We have tried force transfers, purging journal files and nothing seems
to work.
We rolled back the update to one performed earlier in the month and now everything is working.
Anybody have any idea what is going on with this latest update?
We just ran the latest updates for Debian Buster on one of our DNS
servers running bind9 and one of the slave domains is failing with this message:
Aug 2 07:05:20 <hostname> named[76759]: transfer of '<domain name>/IN' from <ip address>#53: Transfer status: too many records
There are about 1,400 records in that domain which has never posed a
problem in the past.
We have tried force transfers, purging journal files and nothing seems
to work.
We rolled back the update to one performed earlier in the month and now everything is working.
Anybody have any idea what is going on with this latest update?
On 02/08/2024 10:10, Brian wrote:
We just ran the latest updates for Debian Buster on one of our DNS
servers running bind9 and one of the slave domains is failing with this message:
Aug 2 07:05:20 <hostname> named[76759]: transfer of '<domain name>/IN' from <ip address>#53: Transfer status: too many records
There are about 1,400 records in that domain which has never posed a problem in the past.
We have tried force transfers, purging journal files and nothing seems
to work.
We rolled back the update to one performed earlier in the month and now everything is working.
Anybody have any idea what is going on with this latest update?
Maybe related to https://kb.isc.org/docs/rrset-limits-in-zones ?
See also
https://lists.debian.org/debian-security-announce/2024/msg00145.html (even
if it does not directly apply to buster).
On Fri, Aug 02, 2024 at 10:15:38AM -0300, Eduardo M KALINOWSKI wrote:
Maybe related to https://kb.isc.org/docs/rrset-limits-in-zones ?That seems unlikely, as the bind9 package in buster have not yet been
See also
https://lists.debian.org/debian-security-announce/2024/msg00145.html (even >> if it does not directly apply to buster).
updated to fix the CVEs referenced in that particular DSA.
Brian, can you provide more details about what specific packages were
updated and from what version to what version? You can find that
information in /var/log/dpkg.log*.
On 02/08/2024 10:44, Roberto C. Sánchez wrote:
On Fri, Aug 02, 2024 at 10:15:38AM -0300, Eduardo M KALINOWSKI wrote:
Maybe related to https://kb.isc.org/docs/rrset-limits-in-zones ?
See also https://lists.debian.org/debian-security-announce/2024/msg00145.html (even
if it does not directly apply to buster).
That seems unlikely, as the bind9 package in buster have not yet been updated to fix the CVEs referenced in that particular DSA.
Brian, can you provide more details about what specific packages were updated and from what version to what version? You can find that information in /var/log/dpkg.log*.
buster has a new upstream version 9.20.0, which includes the new configuration options, and a default limit of 100 for each when they're not set (according the the first link).
On Fri, Aug 2, 2024 at 9:13 AM Brian <kimhick@yahoo.com> wrote:
We just ran the latest updates for Debian Buster on one of our DNS servers running bind9 and one of the slave domains is failing with this message:
Aug 2 07:05:20 <hostname> named[76759]: transfer of '<domain name>/IN' from <ip address>#53: Transfer status: too many records
There are about 1,400 records in that domain which has never posed a problem in the past.
We have tried force transfers, purging journal files and nothing seems to work.
We rolled back the update to one performed earlier in the month and now everything is working.
Anybody have any idea what is going on with this latest update?
I think this might be "bind9 update 9.16.50 -- too many record" from
the debian-security mailing list at <https://lists.debian.org/debian-security/2024/07/msg00003.html>.
That new upstream version (9.20.0) is in sid/trixie. Buster has this:
On Fri, Aug 2, 2024 at 10:37 AM Roberto C. Sánchez <roberto@debian.org> wrote:
On Fri, Aug 02, 2024 at 10:16:51AM -0400, Jeffrey Walton wrote:
On Fri, Aug 2, 2024 at 9:13 AM Brian <kimhick@yahoo.com> wrote:
We just ran the latest updates for Debian Buster on one of our DNS servers running bind9 and one of the slave domains is failing with this message:
Aug 2 07:05:20 <hostname> named[76759]: transfer of '<domain name>/IN' from <ip address>#53: Transfer status: too many records
There are about 1,400 records in that domain which has never posed a problem in the past.
We have tried force transfers, purging journal files and nothing seems to work.
We rolled back the update to one performed earlier in the month and now everything is working.
Anybody have any idea what is going on with this latest update?
I think this might be "bind9 update 9.16.50 -- too many record" from
the debian-security mailing list at <https://lists.debian.org/debian-security/2024/07/msg00003.html>.
Which seems unlikely on a system running buster.
Maybe I am mis-parsing things, but the backporting to older Debian
versions is discussed, starting with the question, "Would you be
willing to backport the configuration of 9.20 so that companies using
larger record number per name can still use bind9 with security
update?" The first answer appears at <https://lists.debian.org/debian-security/2024/07/msg00004.html>.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 165:40:33 |
| Calls: | 10,385 |
| Calls today: | 2 |
| Files: | 14,057 |
| Messages: | 6,416,525 |