This was fixed roughly 6 years ago in a later version of BIND 9.11 which has
since been EoL’d. Upgrade to a supported version.
> On 9 Apr 2025, at 23:22, Duleep Thilakarathne wrote:
>
> Hi,
>
> Bind service unexpectedly exited a few days back with the following error:
> Could someone possibly
Hi,
Bind service unexpectedly exited a few days back with the following error:
Could someone possibly suggest some more troubleshooting? This service has
run for more than a year without issue.
dispatch.c:3422: REQUIRE(resp->item_out == isc_boolean_true) failed, back
trace
#0 0x438bed in ??
#1 0x
Hi Peter, I really appreciate this discourse too. With what's happening in the
world now
and with this particular executive order affecting even something as niche as
DNS, I like
how it offers a vessel to have this public discussion.
On Tuesday, April 8, 2025 7:40:44 PM CEST Peter 'PMc' Much w
On 4/9/25 02:29, Bagas Sanjaya wrote:
On Tue, Apr 08, 2025 at 07:38:44AM -0500, Matthijs Mekking wrote:
This time I was able to reproduce, thanks.
The reason why the key created by dnssec-keygen is retired because named
thinks it was in use already. When there is key timing metadata, the key
On Tue, Apr 08, 2025 at 07:38:44AM -0500, Matthijs Mekking wrote:
> This time I was able to reproduce, thanks.
>
> The reason why the key created by dnssec-keygen is retired because named
> thinks it was in use already. When there is key timing metadata, the key is
> considered to be in use (now o
5 matches
Mail list logo
