Hi James,
I understand this has caused you some discomfort, but it was documented both
in the release notes and in the announcement and it was necessary to introduce
the limits because more fix would have to be intrusive refactoring of the
internals,
and that is exactly the thing that we were try
I should have said, I changed the following parameter to resolve the issue:
max-records-per-type 1000;
--James
On 7/24/24 07:18, James Stegemeyer wrote:
Thanks for the new release, and the hard work you do.
I recently upgraded from 9.18.24 to 9.18.28 per prompting by Ubuntu
USN-6909-1 to pr
Thanks for the new release, and the hard work you do.
I recently upgraded from 9.18.24 to 9.18.28 per prompting by Ubuntu
USN-6909-1 to preform a security update. I deployed this into
production after passing some tests when installed in a lab. After the
upgrade, Internal Zones that were host
I should have refreshed my email before hitting reply.
Thanks Victoria! That is a great summary and I totally agree with the
direction stated.
I don't know that it needs to be included in the announcement itself,
but maybe a link in the announcement to an article describing how it
works on an ong
Ah, thank you! I knew I was missing something. The mailing list should
have been my first place to look. I should have specified
"site:lists.isc.org/pipermail/bind-users/" in my searches.
To summarize the thread Ondřej referenced, this bit from Michał Kępień
explains the plan:
"While I don't have
Adam,
> What is the proper mapping of "Current Stable, ESV", "Development", and "New
> Stable" BIND versions to their respective COPR repos? I feel like it should
> be obvious, but I am missing something.
I did consider whether we should summarize this in the announcement. Perhaps I
should hav
Hi Adam,
this was discussed a month ago:
https://lists.isc.org/pipermail/bind-users/2024-June/108638.html
and we were basically asked to make the bumps in the repositories to not follow
the releases.
Ondrej
--
Ondřej Surý (He/Him)
ond...@isc.org
My working hours and your working hours may be
First, thank you all for the hard work you do on BIND.
What is the proper mapping of "Current Stable, ESV", "Development", and
"New Stable" BIND versions to their respective COPR repos? I feel like it
should be obvious, but I am missing something.
I think I expected 9.18.28 to appear in isc/bind
Brian,
> We use the COPR to install BIND on our servers, and I wanted to mention that
> it looks like in both the isc/bind and isc/bind-esv repos, the build of the
> package “isc-bind-bind” failed for version 9.18.28-1.1 in (as far as I can
> tell) only the EPEL 7 repo in Build 7776636. Could
, BIND Users
Subject: New BIND releases are available: 9.18.28, 9.20.0
BIND users- Our July 2024 maintenance release of BIND 9. 18, as well as the new
9. 20. 0 stable branch, are available and can be downloaded from the ISC
software download page, https: //www. isc. org/download. In addition to bug
BIND users-
Our July 2024 maintenance release of BIND 9.18, as well as the new 9.20.0
stable branch, are available and can be downloaded from the ISC software
download page, https://www.isc.org/download.
In addition to bug fixes and feature improvements, these releases also contain
fixes for s
11 matches
Mail list logo
