resolver priming query complete

Hi, I'm trying to find out what causes named 9.16.20 to print this log message "resolver priming query complete" in irregular intervals. The problem had been reported some time ago (https://gitlab.isc.org/isc-projects/bind9/-/issues/752) but should have been fixed. The named.conf file is p

Re: "doth" test failing in 9.18.3

On 24.05.22 13:27, Michał Kępień wrote: Hi Josef, I'm in the process of upgrading openSUSE Tumbleweed to bind 9.18.3 and in doing so, also run the test suite. However, it fails in step FAIL: doth The log file says I:doth:testing incoming XoT functionality (from the first secondary) (2) I:doth:

"doth" test failing in 9.18.3

Hi, I'm in the process of upgrading openSUSE Tumbleweed to bind 9.18.3 and in doing so, also run the test suite. However, it fails in step FAIL: doth The log file says I:doth:testing incoming XoT functionality (from the first secondary) (2) I:doth:timed out waiting for zone transfer Is there

Re: Building contrib modules for 9.18.2 fails

On 26.04.22 12:25, Michal Nowak wrote: On 25/04/2022 12:20, Josef Moellers wrote: Hi, I'm trying to build bind 9.18.2 with the contrib modules, but this fails for contrib/dlz/modules/wildcard. Without any modifications to the spec file used for 9.18.1, it fails because it does not

Building contrib modules for 9.18.2 fails

Hi, I'm trying to build bind 9.18.2 with the contrib modules, but this fails for contrib/dlz/modules/wildcard. Without any modifications to the spec file used for 9.18.1, it fails because it does not have "FALLTHROUGH" and "UNREACHABLE()", whose use is new in 9.18.2, defined. I tried to so

Re: dns_dnssec_findzonekeys2: error reading WHATEVER.private: file not found

On 23.02.22 15:32, Niall O'Reilly wrote: Hello. Using BIND 9.16.1-Ubuntu (Stable Release) id:d497c32 because that’s what’s most simply available on Ubuntu 20.04.3 LTS (Focal Fossa), I’m seeing messages reporting that private key files can’t be found, such as the one in the subject line. The f

Re: "make test" not working?

On 01.02.22 18:13, Ondřej Surý wrote: On 1. 2. 2022, at 15:28, Josef Moellers wrote: Thanks, Ondřej, for pushing my nose onto the fact that the test should be run as a non-privileged user. BTDTGT Well, you are welcome, but please **do** include all the modifications and all the steps you

Re: "make test" not working?

On 01.02.22 17:54, Reindl Harald wrote: Am 01.02.22 um 15:28 schrieb Josef Moellers: Just for the record: Thanks, Ondřej, for pushing my nose onto the fact that the test should be run as a non-privileged user. really *nothing* should run as root, especially not building software - doing

Re: "make test" not working?

Hi folks, Just for the record: Thanks, Ondřej, for pushing my nose onto the fact that the test should be run as a non-privileged user. BTDTGT As I am determined (and it makes sense) to run the tests on the binaries that we will eventually ship, I need to build the software according to our

Re: "make test" not working?

On 31.01.22 21:24, Evan Hunt wrote: On Mon, Jan 31, 2022 at 05:36:28PM +0100, Ondřej Surý wrote: This works: $ mkdir /tmp/bind9 $ cd /tmp/bind9 $ curl -sSLO https://downloads.isc.org/isc/bind9/9.18.0/bind-9.18.0.tar.xz $ tar -xJf bind-9.18.0.tar.xz $ cd bind-9.18.0/ $ ./configure $ make -j A

Re: "make test" not working?

On 31.01.22 16:57, Ondřej Surý wrote: Hi, On 31. 1. 2022, at 15:42, Josef Moellers wrote: Hi, Me again ... I have installed the files required to build the packages on an openSUSE Tumbleweed machine. I have also added --enable-developer --disable-warn-error to the configure options

Re: "make test" not working?

On 31.01.22 15:42, Josef Moellers wrote: Hi, Me again ... I have installed the files required to build the packages on an openSUSE Tumbleweed machine. I have also added     --enable-developer --disable-warn-error to the configure options. Yet "make test" fails in that it d

"make test" not working?

Hi, Me again ... I have installed the files required to build the packages on an openSUSE Tumbleweed machine. I have also added --enable-developer --disable-warn-error to the configure options. Yet "make test" fails in that it does not do anything. "make check" does run some tests, but

Python support

Mooi'n, I was wondering: 9.16.x (and older versions) had "Python functions to support BIND utilities", including some scripts: * dnssec-checkds * dnssec-coverage * dnssec-keymgr They are not present in 9.18.0, but I find no notice of this support being dropped in the release notes nor in the C

Re: New BIND releases are available: 9.11.32, 9.16.16, and 9.17.13

On 20.05.21 17:22, Manish Rane wrote: > Hi Team, > > Are those new versions available in Linux distro packages? As Anand already wrote: our Enterprise releases won't have this atm, unless you request it through the official channels. OpenSUSE Tumbleweed will hopefully have in a few days. Josef >

Re: /etc/bind.keys in a chrooted environment

On 22.07.20 17:05, Anand Buddhdev wrote: > On 22/07/2020 16:51, Josef Moellers wrote: > >> It turns out that it is mainly the warning the partner is irritade about. >> >> So, let me put the question the other way round: what would happen if we >> *always* copie

Re: /etc/bind.keys in a chrooted environment

On 22.07.20 16:41, Anand Buddhdev wrote: > On 22/07/2020 15:30, Josef Moellers wrote: > >>> Or just ignore the warning, and let BIND use its built-in keys. >> >> If /etc/bind.keys contains some additional keys, this will not work ;-) > > Sure, but what additiona

Re: /etc/bind.keys in a chrooted environment

On 22.07.20 15:28, Anand Buddhdev wrote: > On 22/07/2020 15:06, Josef Moellers wrote: > > Hi Josef, > >> named complains about the missing file /etc/bind.keys if run chrooted: >> unable to open '/etc/bind.keys' using built-in keys >> >> What is the

/etc/bind.keys in a chrooted environment

Hi, named complains about the missing file /etc/bind.keys if run chrooted: unable to open '/etc/bind.keys' using built-in keys What is the preferred way around this? Add "/etc/bind-keys" to NAMED_CONF_INCLUDE_FILES? Thanks, Josef -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürn