ISC Open Source Projects issueshttps://gitlab.isc.org/groups/isc-projects/-/issues2022-01-04T12:33:56Zhttps://gitlab.isc.org/isc-projects/stork/-/issues/264problem with parsing kea config with comments2022-01-04T12:33:56ZMichal Nowikowskiproblem with parsing kea config with commentsWhen `http-port` setting in kea config is commented out then agent will incorrectly take it as valid setting.When `http-port` setting in kea config is commented out then agent will incorrectly take it as valid setting.1.1Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/kea/-/issues/1216Modify the DDNS FQDN format from DHCP42020-05-20T15:05:36ZvarsrajaModify the DDNS FQDN format from DHCP4
Kea version : 1.6.2
Services used: DHCP4 , DHCP-DDNS
Issue:
I would like to modify how the default FQDN is generated in the DHCP4 server for DDNS update.
By default we have the <prefix>-<IP-address-hyphenated>.<suffix> [eg abc-x...
Kea version : 1.6.2
Services used: DHCP4 , DHCP-DDNS
Issue:
I would like to modify how the default FQDN is generated in the DHCP4 server for DDNS update.
By default we have the <prefix>-<IP-address-hyphenated>.<suffix> [eg abc-x.x.x.x.mnp.com].
I would like to generate the same using mac address instead of ip-address [eg abc-macaddress.mnp.com]
1. Is there any configuration that is available to achieve this?
2. Can someone please let me know if I will be able to write a hook to achieve this.
Ps: I referred to following mail threads but am not able to access the bug tickets mentioned in them.
1. https://lists.isc.org/pipermail/kea-users/2016-January/000205.html
2. http://kea-users.7364.n8.nabble.com/Kea-users-Issue-with-DDNS-updates-td229.html#a234
Thanks
VarshaThomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/kea/-/issues/1215Pkt<4/6>::getName() should support all message type names2020-05-13T14:33:40ZThomas MarkwalderPkt<4/6>::getName() should support all message type namesNotably missing from Pkt4::getName() are the lease query related message types. It would be handy if we returned labels for all the types, not just those we handle.Notably missing from Pkt4::getName() are the lease query related message types. It would be handy if we returned labels for all the types, not just those we handle.kea1.7.8Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/1213fix sphinx list rendering2020-05-13T14:42:15ZFrancis Dupontfix sphinx list renderingSphinx seems a bit picky about list, for instance:
```
- ``foo`` - explain foo here
and bla bla...
```
is not rendered as:
```
- ``foo`` - explain foo here
and this bugs?
```
This issue should fix all instances of this problem ...Sphinx seems a bit picky about list, for instance:
```
- ``foo`` - explain foo here
and bla bla...
```
is not rendered as:
```
- ``foo`` - explain foo here
and this bugs?
```
This issue should fix all instances of this problem kept by translation to sphinx.kea1.7.8Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/bind9/-/issues/1811Follow-up from "Don't set recv/send buffer sizes for udp sockets in netmgr."2020-05-05T12:59:18ZOndřej SurýFollow-up from "Don't set recv/send buffer sizes for udp sockets in netmgr."The following discussion from !3476 should be addressed:
- [ ] @ondrej started a [discussion](https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/3476#note_128851): (+1 comment)
> I would suggest killing the same code in th...The following discussion from !3476 should be addressed:
- [ ] @ondrej started a [discussion](https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/3476#note_128851): (+1 comment)
> I would suggest killing the same code in the old networking code.May 2020 (9.11.19, 9.11.19-S1, 9.14.12, 9.16.3)https://gitlab.isc.org/isc-projects/bind9/-/issues/1810Refactor ecdsa and eddsa tests after testcrypto.sh changes2021-03-02T13:53:54ZOndřej SurýRefactor ecdsa and eddsa tests after testcrypto.sh changesBoth `ecdsa` and `eddsa` tests treat all algorithms in set as either all supported or all unsupported.
This makes it hard to incrementally add more algorithms and it also doesn't match reality (ED448 was added to OpenSSL much later than...Both `ecdsa` and `eddsa` tests treat all algorithms in set as either all supported or all unsupported.
This makes it hard to incrementally add more algorithms and it also doesn't match reality (ED448 was added to OpenSSL much later than ED25519).March 2021 (9.11.29, 9.11.29-S1, 9.16.13, 9.16.13-S1, 9.17.11)Matthijs Mekkingmatthijs@isc.orgMatthijs Mekkingmatthijs@isc.orghttps://gitlab.isc.org/isc-projects/bind9/-/issues/1809Release Checklist for BIND 9.11.19, BIND 9.11.19-S1, BIND 9.14.12, BIND 9.16.32020-06-10T09:16:50ZMichał KępieńRelease Checklist for BIND 9.11.19, BIND 9.11.19-S1, BIND 9.14.12, BIND 9.16.3## Release Schedule
**Code Freeze:** Friday, May 1st, 2020
**Tagging Deadline:** Wednesday, May 6th, 2020
**Public Release:** Tuesday, May 19th, 2020
## Release Checklist
### Before the Code Freeze
- [x] ***(QA)*** Inform Support ...## Release Schedule
**Code Freeze:** Friday, May 1st, 2020
**Tagging Deadline:** Wednesday, May 6th, 2020
**Public Release:** Tuesday, May 19th, 2020
## Release Checklist
### Before the Code Freeze
- [x] ***(QA)*** Inform Support and Marketing of impending release (and give estimated release dates).
- [x] ***(QA)*** Ensure there are no permanent test failures on any platform.
- [x] ***(QA)*** Check Perflab to ensure there has been no unexplained drop in performance for the versions being released.
- [x] ***(QA)*** Check whether all issues assigned to the release milestone are resolved[^1].
- [x] ***(QA)*** Ensure that there are no outstanding merge requests in the private repository[^1] (Subscription Edition only).
- [x] ***(QA)*** Ensure all merge requests marked for backporting have been indeed backported.
### Before the Tagging Deadline
- [x] ***(QA)*** Look for outstanding documentation issues (e.g. `CHANGES` mistakes) and address them if any are found.
- [x] ***(QA)*** Ensure release notes are correct, ask Support and Marketing to check them as well.
- [x] ***(Support)*** Check release notes, ask QA to correct any mistakes found.
- [x] ***(Marketing)*** Check release notes, ask QA to correct any mistakes found.
- [x] ***(SwEng)*** Update API files for libraries with new version information.
- [x] ***(SwEng)*** Change software version and library versions in `configure.ac` (new major release only).
- [x] ***(SwEng)*** Rebuild `configure` using Autoconf on `docs.isc.org`.
- [x] ***(SwEng)*** Update `CHANGES`.
- [x] ***(SwEng)*** Update `CHANGES.SE` (Subscription Edition only).
- [x] ***(SwEng)*** Update `README.md`.
- [x] ***(SwEng)*** Update `version`.
- [x] ***(SwEng)*** Build documentation on `docs.isc.org`.
- [x] ***(QA)*** Check that all the above steps were performed correctly.
- [x] ***(QA)*** Check that the formatting is correct for text, PDF, and HTML versions of release notes.
- [x] ***(SwEng)*** Tag the releases[^2]. (Tags may only be pushed to the public repository for releases which are *not* security releases.)
- [x] ***(SwEng)*** If this is the first tag for a release (e.g. beta), create a release branch named `release_v9_X_Y` to allow development to continue on the maintenance branch whilst release engineering continues.
### Before the ASN Deadline (for ASN Releases) or the Public Release Date (for Regular Releases)
- [x] ***(QA)*** Verify GitLab CI results for the tags created and prepare a QA report for the releases to be published.
- [x] ***(QA)*** Request signatures for the tarballs, providing their location and checksums.
- [x] ***(Signers)*** Validate tarball checksums, sign tarballs, and upload signatures.
- [x] ***(QA)*** Verify tarball signatures and check tarball checksums again.
- [x] ***(Support)*** Pre-publish ASN and/or Subscription Edition tarballs so that packages can be built.
- [x] ***(QA)*** Build and test ASN and/or Subscription Edition packages.
- [x] ***(QA)*** Notify Support that the releases have been prepared.
- [x] ***(Support)*** Send out ASNs (if applicable).
### On the Day of Public Release
- [x] ***(Support)*** Wait for clearance from Security Officer to proceed with the public release (if applicable).
- [x] ***(Support)*** Place tarballs in public location on FTP site.
- [x] ***(Support)*** Publish links to downloads on ISC website.
- [x] ***(Support)*** Write release email to *bind-announce*.
- [x] ***(Support)*** Write email to *bind-users* (if a major release).
- [x] ***(Support)*** Update tickets in case of waiting support customers.
- [x] ***(QA)*** Build and test any outstanding private packages.
- [x] ***(QA)*** Build public packages (`*.deb`, RPMs).
- [x] ***(QA)*** Inform Marketing of the release.
- [x] ***(QA)*** Update the internal [BIND release dates wiki page](https://wiki.isc.org/bin/view/Main/BindReleaseDates) when public announcement has been made.
- [x] ***(Marketing)*** Post short note to Twitter.
- [x] ***(Marketing)*** Update [Wikipedia entry for BIND](https://en.wikipedia.org/wiki/BIND).
- [x] ***(Marketing)*** Write blog article (if a major release).
- [x] ***(QA)*** Ensure all new tags are annotated and signed.
- [x] ***(SwEng)*** Push tags for the published releases to the public repository.
- [x] ***(SwEng)*** Merge the automatically prepared `prep 9.X.Y` commit which updates `version` and documentation on the release branch into the relevant maintenance branch (`v9_X`).
- [x] ***(QA)*** For each maintained branch, update the `BIND_BASELINE_VERSION` variable for the `abi-check:sid:amd64` job in `.gitlab-ci.yml` to the latest published BIND version tag for a given branch.
- [x] ***(QA)*** Prepare empty release notes for the next set of releases.
[^1]: If not, use the time remaining until the tagging deadline to ensure all outstanding issues are either resolved or moved to a different milestone.
[^2]: Preferred command line: `git tag -u <DEVELOPER_KEYID> -a -s -m "BIND 9.X.Y[alphatag]" v9_X_Y[alphatag]`, where `[alphatag]` is an optional string such as `b1`, `rc1`, etc.May 2020 (9.11.19, 9.11.19-S1, 9.14.12, 9.16.3)Vicky Riskvicky@isc.orgVicky Riskvicky@isc.org2020-05-19https://gitlab.isc.org/isc-projects/bind9/-/issues/1808assertion failure in bind 9.16.22020-06-08T12:52:05ZOndřej Surýassertion failure in bind 9.16.2As reported to SO:
```
> Hello there,
>
> I'm running some dnsperf test against from in your testlab, and quite often i bind to crash with assertion failure.
>
> I'm running bind dnsperf with: dnsperf -f inet -t 10 -s <SANITIZED> -d...As reported to SO:
```
> Hello there,
>
> I'm running some dnsperf test against from in your testlab, and quite often i bind to crash with assertion failure.
>
> I'm running bind dnsperf with: dnsperf -f inet -t 10 -s <SANITIZED> -d dns_clear.txt -c 200 -T 4 -l 36000000 -q 5000 -S 1 (Attached dns_clear.txt, which is are reallife traffic dump from our prod bind servers). We're running CentOS Linux release 7.7.1908 (Core) in both test/prod.
>
> 29-Apr-2020 15:45:27.651 general: critical: netaddr.c:365: INSIST(0) failed, back trace
> 29-Apr-2020 15:45:27.651 general: critical: #0 0x42b890 in ??
> 29-Apr-2020 15:45:27.651 general: critical: #1 0x7f033062cada in ??
> 29-Apr-2020 15:45:27.651 general: critical: #2 0x7f033064a3d3 in ??
> 29-Apr-2020 15:45:27.651 general: critical: #3 0x7f033064fcc0 in ??
> 29-Apr-2020 15:45:27.651 general: critical: #4 0x7f033064ff56 in ??
> 29-Apr-2020 15:45:27.651 general: critical: #5 0x7f033195feaa in ??
> 29-Apr-2020 15:45:27.651 general: critical: #6 0x7f033187c448 in ??
> 29-Apr-2020 15:45:27.651 general: critical: #7 0x7f0331972a40 in ??
> 29-Apr-2020 15:45:27.651 general: critical: #8 0x7f0330652ada in ??
> 29-Apr-2020 15:45:27.651 general: critical: #9 0x7f032edc2e65 in ??
> 29-Apr-2020 15:45:27.651 general: critical: #10 0x7f032e6cd88d in ??
> 29-Apr-2020 15:45:27.651 general: critical: exiting (due to assertion failure)
>
> I've several coredumps.. Do you guys have a place where i can upload them?
>
> [root@srv07 data]# ls -lh
> total 5.7G
> -rw-------. 1 named named 1.7G Apr 22 08:48 core.11065
> -rw-------. 1 named named 1.6G Apr 22 12:58 core.11877
> -rw-------. 1 named named 2.6G Apr 21 21:17 core.126377
> -rw-------. 1 named named 1.4G Apr 29 15:45 core.15168
> -rw-------. 1 named named 166M Apr 27 17:03 core.21234
> -rw-------. 1 named named 175M Apr 27 17:07 core.21301
> -rw-------. 1 named named 2.2G Apr 21 15:33 core.72474
>
> [root@srv07 log]# named -V
> BIND 9.16.2 (Stable Release) <id:b310dc7>
> running on Linux x86_64 3.10.0-1062.18.1.el7.x86_64 #1 SMP Tue Mar 17 23:49:17 UTC 2020
> built by make with '--build=x86_64-redhat-linux-gnu' '--host=x86_64-redhat-linux-gnu' '--program-prefix=' '--disable-dependency-tracking' '--prefix=/opt/isc/isc-bind/root/usr' '--exec-prefix=/opt/isc/isc-bind/root/usr' '--bindir=/opt/isc/isc-bind/root/usr/bin' '--sbindir=/opt/isc/isc-bind/root/usr/sbin' '--sysconfdir=/etc/opt/isc/isc-bind' '--datadir=/opt/isc/isc-bind/root/usr/share' '--includedir=/opt/isc/isc-bind/root/usr/include' '--libdir=/opt/isc/isc-bind/root/usr/lib64' '--libexecdir=/opt/isc/isc-bind/root/usr/libexec' '--localstatedir=/var/opt/isc/isc-bind' '--sharedstatedir=/var/opt/isc/isc-bind/lib' '--mandir=/opt/isc/isc-bind/root/usr/share/man' '--infodir=/opt/isc/isc-bind/root/usr/share/info' '--disable-static' '--enable-dnstap' '--with-pic' '--with-gssapi' '--with-json-c' '--with-libtool' '--with-libxml2' '--without-lmdb' '--with-docbook-xsl=/usr/share/sgml/docbook/xsl-stylesheets' '--with-python' 'build_alias=x86_64-redhat-linux-gnu' 'host_alias=x86_64-redhat-linux-gnu' 'CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic' 'LDFLAGS= -L/opt/isc/isc-bind/root/usr/lib64' 'PKG_CONFIG_PATH=:/opt/isc/isc-bind/root/usr/lib64/pkgconfig:/opt/isc/isc-bind/root/usr/share/pkgconfig'
> compiled by GCC 4.8.5 20150623 (Red Hat 4.8.5-39)
> compiled with OpenSSL version: OpenSSL 1.0.2k-fips 26 Jan 2017
> linked to OpenSSL version: OpenSSL 1.0.2k-fips 26 Jan 2017
> compiled with libxml2 version: 2.9.1
> linked to libxml2 version: 20901
> compiled with json-c version: 0.11
> linked to json-c version: 0.11
> compiled with zlib version: 1.2.7
> linked to zlib version: 1.2.7
> compiled with protobuf-c version: 1.3.2
> linked to protobuf-c version: 1.3.2
> threads support is enabled
>
> default paths:
> named configuration: /etc/opt/isc/isc-bind/named.conf
> rndc configuration: /etc/opt/isc/isc-bind/rndc.conf
> DNSSEC root key: /etc/opt/isc/isc-bind/bind.keys
> nsupdate session key: /var/opt/isc/isc-bind/run/named/session.key
> named PID file: /var/opt/isc/isc-bind/run/named/named.pid
> named lock file: /var/opt/isc/isc-bind/run/named/named.lock
>
>
>
> [root@srv07 log]# ldd /opt/isc/isc-bind/root/usr/sbin/named
> linux-vdso.so.1 => (0x00007ffcc594a000)
> libns.so.1602 => /opt/isc/isc-bind/root/usr/lib64/libns.so.1602 (0x00007f8aa0acf000)
> libdns.so.1602 => /opt/isc/isc-bind/root/usr/lib64/libdns.so.1602 (0x00007f8aa06a6000)
> libbind9.so.1600 => /opt/isc/isc-bind/root/usr/lib64/libbind9.so.1600 (0x00007f8aa0493000)
> libisccfg.so.1600 => /opt/isc/isc-bind/root/usr/lib64/libisccfg.so.1600 (0x00007f8aa0261000)
> libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f8aa0014000)
> libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f8a9fd2b000)
> libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f8a9faf8000)
> libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f8a9f8f4000)
> libisccc.so.1600 => /opt/isc/isc-bind/root/usr/lib64/libisccc.so.1600 (0x00007f8a9f6ea000)
> libisc.so.1602 => /opt/isc/isc-bind/root/usr/lib64/libisc.so.1602 (0x00007f8a9f475000)
> libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f8a9f012000)
> libjson-c.so.2 => /lib64/libjson-c.so.2 (0x00007f8a9ee07000)
> libxml2.so.2 => /lib64/libxml2.so.2 (0x00007f8a9ea9d000)
> libz.so.1 => /lib64/libz.so.1 (0x00007f8a9e887000)
> libcap.so.2 => /lib64/libcap.so.2 (0x00007f8a9e682000)
> libprotobuf-c.so.1 => /opt/isc/isc-bind/root/usr/lib64/libprotobuf-c.so.1 (0x00007f8a9e479000)
> libfstrm.so.0 => /opt/isc/isc-bind/root/usr/lib64/libfstrm.so.0 (0x00007f8a9e26e000)
> libuv.so.1 => /opt/isc/isc-bind/root/usr/lib64/libuv.so.1 (0x00007f8a9e03f000)
> librt.so.1 => /lib64/librt.so.1 (0x00007f8a9de37000)
> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f8a9dc1b000)
> libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f8a9da01000)
> libdl.so.2 => /lib64/libdl.so.2 (0x00007f8a9d7fd000)
> libc.so.6 => /lib64/libc.so.6 (0x00007f8a9d42f000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f8aa0d16000)
> libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f8a9d21f000)
> libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f8a9d01b000)
> libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f8a9ce02000)
> liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f8a9cbdc000)
> libm.so.6 => /lib64/libm.so.6 (0x00007f8a9c8da000)
> libattr.so.1 => /lib64/libattr.so.1 (0x00007f8a9c6d5000)
> libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f8a9c4ae000)
> libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f8a9c24c000)
```
The reporter is using our packages:
> We've installed bind directly from your CentOS repo; Do you still want us to send your debug symbols?
and the coredumps have been uploaded to my <SANITIZED>.June 2020 (9.11.20, 9.11.20-S1, 9.16.4, 9.17.2)Witold KrecickiWitold Krecickihttps://gitlab.isc.org/isc-projects/bind9/-/issues/1807"named-checkconf -z" exit status reflects only the last view loaded2022-01-24T16:35:07ZGraham Clinch"named-checkconf -z" exit status reflects only the last view loaded<!--
If the bug you are reporting is potentially security-related - for example,
if it involves an assertion failure or other crash in `named` that can be
triggered repeatedly - then please do *NOT* report it here, but send an
email to [...<!--
If the bug you are reporting is potentially security-related - for example,
if it involves an assertion failure or other crash in `named` that can be
triggered repeatedly - then please do *NOT* report it here, but send an
email to [security-officer@isc.org](security-officer@isc.org).
-->
### Summary
When processing a named.conf with views, the exit status of 'named-checkconf -z' only reflects whether there were errors whilst loading the final view, even though all zones in all views are processed and errors printed as appropriate.
### BIND version used
```
BIND 9.16.2 (Stable Release) <id:b310dc7>
running on Darwin x86_64 19.4.0 Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64
built by make with '--prefix=/usr/local/Cellar/bind/9.16.2' '--with-json-c' '--with-openssl=/usr/local/opt/openssl@1.1' '--with-libjson=/usr/local/opt/json-c' '--with-python-install-dir=/usr/local/Cellar/bind/9.16.2/libexec/vendor/lib/python3.8/site-packages' '--with-python=/usr/local/opt/python@3.8/bin/python3' '--without-lmdb' 'CC=clang' 'PKG_CONFIG_PATH=/usr/local/opt/json-c/lib/pkgconfig:/usr/local/opt/libuv/lib/pkgconfig:/usr/local/opt/openssl@1.1/lib/pkgconfig:/usr/local/opt/readline/lib/pkgconfig:/usr/local/opt/sqlite/lib/pkgconfig:/usr/local/opt/xz/lib/pkgconfig:/usr/local/opt/python@3.8/lib/pkgconfig' 'PKG_CONFIG_LIBDIR=/usr/lib/pkgconfig:/usr/local/Homebrew/Library/Homebrew/os/mac/pkgconfig/10.15'
compiled by CLANG 4.2.1 Compatible Apple LLVM 11.0.3 (clang-1103.0.32.59)
compiled with OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020
linked to OpenSSL version: OpenSSL 1.1.1g 21 Apr 2020
compiled with libxml2 version: 2.9.4
linked to libxml2 version: 20904
compiled with json-c version: 0.13.1
linked to json-c version: 0.13.1
compiled with zlib version: 1.2.11
linked to zlib version: 1.2.11
threads support is enabled
default paths:
named configuration: /usr/local/Cellar/bind/9.16.2/etc/named.conf
rndc configuration: /usr/local/Cellar/bind/9.16.2/etc/rndc.conf
DNSSEC root key: /usr/local/Cellar/bind/9.16.2/etc/bind.keys
nsupdate session key: /usr/local/Cellar/bind/9.16.2/var/run/named/session.key
named PID file: /usr/local/Cellar/bind/9.16.2/var/run/named/named.pid
named lock file: /usr/local/Cellar/bind/9.16.2/var/run/named/named.lock
```
### Steps to reproduce
Given the configuration files listed later on, and intentionally creating an error by not creating a missing.net zone file:
Running named-checkconf -z against named-missing-last.conf gives an exit status of 1 as expected:
```
$ named-checkconf -d -z named-missing-last.conf
loading "example.net" from "example.net" class "IN"
zone example.net/IN: loaded serial 1
loading "missing.net" from "missing.net" class "IN"
zone missing.net/IN: loading from master file missing.net failed: file not found
zone missing.net/IN: not loaded due to errors.
missing/missing.net/IN: file not found
$ echo $?
1
```
Running named-checkconf -z against named-missing-first.conf should also give an exit status of 1, but does not:
```
$ named-checkconf -d -z named-missing-first.conf
loading "missing.net" from "missing.net" class "IN"
zone missing.net/IN: loading from master file missing.net failed: file not found
zone missing.net/IN: not loaded due to errors.
missing/missing.net/IN: file not found
loading "example.net" from "example.net" class "IN"
zone example.net/IN: loaded serial 1
$ echo $?
0
```
### What is the current *bug* behavior?
The exit status of named-checkconf -z reflects whether there was an error loading the zones in the *final* view.
### What is the expected *correct* behavior?
The exit status of named-checkconf -z should reflect whether there was an error loading the zones in *any* view.
### Relevant configuration files
named-missing-first.conf:
```
view "missing" {
zone "missing.net" {
type master;
file "missing.net";
};
};
view "example" {
zone "example.net" {
type master;
file "example.net";
};
};
```
named-missing-last.conf:
```
view "example" {
zone "example.net" {
type master;
file "example.net";
};
};
view "missing" {
zone "missing.net" {
type master;
file "missing.net";
};
};
```
example.net zone file:
```
$TTL 5
@ SOA ns1.example.net. hostmaster.example.net. 1 300 300 300 300
@ NS ns1.example.net.
ns1 A 127.0.0.1
```
*and no missing.net zone file*
### Possible fixes
bin/check/named-checkconf.c: load_zones_fromconfig() - 'result' (taken from 'tresult') variable appears to be reset by each call to configure_view.May 2020 (9.11.19, 9.11.19-S1, 9.14.12, 9.16.3)https://gitlab.isc.org/isc-projects/kea/-/issues/1212Advice for avoiding HA deadlock2020-05-01T05:58:50ZPeter DaviesAdvice for avoiding HA deadlockUpdate documentation to describe the steps needed to re-enable HA after clocking gets out of skew and avoid recurrent HA deadlock.
Refers to RT [16311](https://support.isc.org/Ticket/Display.html?id=16311)Update documentation to describe the steps needed to re-enable HA after clocking gets out of skew and avoid recurrent HA deadlock.
Refers to RT [16311](https://support.isc.org/Ticket/Display.html?id=16311)https://gitlab.isc.org/isc-projects/dhcp/-/issues/103LICENSE file has confusing preamble2022-01-20T16:13:29ZTomek MrugalskiLICENSE file has confusing preambleThe code is now published under MPL-2.0 license, but the there is extra preamble is slightly confusing.The code is now published under MPL-2.0 license, but the there is extra preamble is slightly confusing.4.4.3-beta1https://gitlab.isc.org/isc-projects/kea/-/issues/1211Compilation warnings on Ubuntu 19.10/g++ 9.2.12020-06-15T15:46:01ZTomek MrugalskiCompilation warnings on Ubuntu 19.10/g++ 9.2.1There are several compilation warnings:
```
labelsequence_unittest.cc: In member function ‘virtual void {anonymous}::ExtendableLabelSequenceTest_extendableLabelSequence_Test::TestBody()’:
labelsequence_unittest.cc:998:33: warning: impli...There are several compilation warnings:
```
labelsequence_unittest.cc: In member function ‘virtual void {anonymous}::ExtendableLabelSequenceTest_extendableLabelSequence_Test::TestBody()’:
labelsequence_unittest.cc:998:33: warning: implicitly-declared ‘constexpr isc::dns::LabelSequence& isc::dns::LabelSequence::operator=(const isc::dns::LabelSequence&)’ is deprecated [-Wdeprecated-copy]
998 | els = LabelSequence(ls1, buf);
| ^
In file included from labelsequence_unittest.cc:11:
../../../../src/lib/dns/labelsequence.h:125:5: note: because ‘isc::dns::LabelSequence’ has user-provided ‘isc::dns::LabelSequence::LabelSequence(const isc::dns::LabelSequence&)’
125 | LabelSequence(const LabelSequence& ls):
| ^~~~~~~~~~~~~
```
(repeated many times throughout the file.
```
cfg_option_unittest.cc: In member function ‘virtual void {anonymous}::CfgOptionTest_replace_Test::TestBody()’:
cfg_option_unittest.cc:297:28: warning: implicitly-declared ‘isc::dhcp::OptionDescriptor& isc::dhcp::OptionDescriptor::operator=(const isc::dhcp::OptionDescriptor&)’ is deprecated [-Wdeprecated-copy]
297 | desc = cfg.get("isc", 2);
| ^
In file included from cfg_option_unittest.cc:17:
../../../../src/lib/dhcpsrv/cfg_option.h:104:5: note: because ‘isc::dhcp::OptionDescriptor’ has user-provided ‘isc::dhcp::OptionDescriptor::OptionDescriptor(const isc::dhcp::OptionDescriptor&)’
104 | OptionDescriptor(const OptionDescriptor& desc)
| ^~~~~~~~~~~~~~~~
```
This also affects client_class_def_unittest.cc, cfg_subnets4_unittest.cc, subnet_unittest.cc and config_backend_unittest.cc (and possibly more.kea1.7.9Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/stork/-/issues/263Need to show global Host Reservations2020-05-06T17:17:24ZTomek MrugalskiNeed to show global Host ReservationsAs pointed out in https://gitlab.isc.org/isc-projects/stork/-/issues/45#note_127068, Stork does not show global (with subnet-id=0) reservations. It should.As pointed out in https://gitlab.isc.org/isc-projects/stork/-/issues/45#note_127068, Stork does not show global (with subnet-id=0) reservations. It should.0.7Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/1210address doxygen errors2020-05-14T21:57:14ZFrancis Dupontaddress doxygen errorsOn my system 70 are reported... BTW what is the official check for this (i.e. Jenkins process name)?On my system 70 are reported... BTW what is the official check for this (i.e. Jenkins process name)?kea1.7.8Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/1209update description of isc-kea-common package2020-06-19T15:01:11ZWlodzimierz Wencelupdate description of isc-kea-common packageAs @marcin pointed out during sanity checks:
` The description of the isc-kea-common package only says it provides the common libraries and doesn't mention hooks.`
Please update description.As @marcin pointed out during sanity checks:
` The description of the isc-kea-common package only says it provides the common libraries and doesn't mention hooks.`
Please update description.kea1.7.9https://gitlab.isc.org/isc-projects/kea/-/issues/1208kea version bump up2020-04-30T09:24:10ZWlodzimierz Wencelkea version bump upchange version to 1.7.8 on masterchange version to 1.7.8 on masterkea1.7.8Wlodzimierz WencelWlodzimierz Wencelhttps://gitlab.isc.org/isc-projects/stork/-/issues/262cleanup of files in backend/server/restservice is needed2020-05-06T12:10:41ZMichal Nowikowskicleanup of files in backend/server/restservice is neededmake file names consistentmake file names consistent0.7Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/bind9/-/issues/1806system and unit clang:asan have incorrect needs2020-05-01T06:41:29ZMark Andrewssystem and unit clang:asan have incorrect needsMay 2020 (9.11.19, 9.11.19-S1, 9.14.12, 9.16.3)https://gitlab.isc.org/isc-projects/bind9/-/issues/1805Save failed build artifacts.2021-08-26T04:24:18ZMark AndrewsSave failed build artifacts.If a build fails having the artifacts retrievable is useful.If a build fails having the artifacts retrievable is useful.September 2021 (9.16.21, 9.16.21-S1, 9.17.18)https://gitlab.isc.org/isc-projects/bind9/-/issues/1804util/parse_tsan.py is not pylint clean2020-04-30T07:38:43ZMark Andrewsutil/parse_tsan.py is not pylint cleanMay 2020 (9.11.19, 9.11.19-S1, 9.14.12, 9.16.3)