Hi Mark
Thank you for your answer. BIND is definitely running the current version:
$ rndc status
version: BIND 9.16.0 (Stable Release) ()
running on server: Linux x86_64 3.10.0-1062.4.3.el7.x86_64 #1 SMP Wed
Nov 13 23:58:53 UTC 2019
boot time: Thu, 20 Feb 2020 16:30:15 GMT
last configured: Th
Tom,
I would run ‘rndc status’ or ‘dig ch txt version.bind @server’ and confirm
that you have restarted named with the new code. I’ve had hundreds of 'bug
reports’ about non fixed bugs that where operators failing to restart named
after
installing the new version. The new code is in 9.16.0,
Hi Matthew,
we’ll write some generic instruction on how to get a coredump from a running
named
(without crashing it) - generally you want to use gcore[1].
Then here you can continue as if the named has crashed and get us a thread
stack trace[2].
As we need to access very specific data structur
Hi Tom,
> On 20 Feb 2020, at 17:42, Tom wrote:
>
> Hi
>
> With 9.16.0, the CDS deletion
> (https://gitlab.isc.org/isc-projects/bind9/issues/1554) is still not working
> and is ending with the same error as bind-versions before:
>
> 20-Feb-2020 17:31:25.381 general: error: zone example.com/IN
Hi
With 9.16.0, the CDS deletion
(https://gitlab.isc.org/isc-projects/bind9/issues/1554) is still not
working and is ending with the same error as bind-versions before:
20-Feb-2020 17:31:25.381 general: error: zone example.com/IN (unsigned):
CDS/CDNSKEY consistency checks failed
20-Feb-2020
On 2/19/20 7:41 PM, Mark Andrews wrote:
> clang-format reordered the includes alphabetically and “dir.h” depends
> on “dlz_minimal.h” for the typedef.
>
> The following should address this.
>
> diff --git a/contrib/dlz/modules/filesystem/dir.h
> b/contrib/dlz/modules/filesystem/dir.h
> index e93
On Wed, Feb 19, 2020 at 11:26 PM Dennis Clarke via bind-users
wrote:
>
> On 2020-02-19 16:01, Andreas Hasenack wrote:
> > Hi,
> >
> > I didn't find a bind-devel mailing list, so I'm sending this here.
> >
> > After a plain ./configure && make install, I see in the installed
> > task.h header file
On 20/02/2020 09:08, Ondřej Surý wrote:
Ah, thank you for this Ondrej! I've adjusted our spec file, and removed
the define.
> Hi Anand,
>
> on the contrary, we set tuning to large by default (it’s default or
> small now), so with the define you are actually setting it to lower value:
>
> #ifnde
Hi Anand,
on the contrary, we set tuning to large by default (it’s default or small now),
so with the define you are actually setting it to lower value:
#ifndef ISC_SOCKET_MAXEVENTS
#ifdef TUNE_LARGE
#define ISC_SOCKET_MAXEVENTS 2048
#else /* ifdef TUNE_LARGE */
#define ISC_SOCKET_MAXEVENTS 64
#
Hi BIND developers,
We build our own RPMs of BIND, and ever since the 9.9 builds, we have
been setting -DISC_SOCKET_MAXEVENTS=256. This is based on advice we
received from someone at ISC.
Is this setting still relevant in BIND 9.16?
Regards,
Anand
___
10 matches
Mail list logo
