BIND issueshttps://gitlab.isc.org/isc-projects/bind9/-/issues2020-06-29T13:05:52Zhttps://gitlab.isc.org/isc-projects/bind9/-/issues/1929[v9_11] Drop "#define activeemtpynode activeemtpynode64" from lib/dns/rbtdb.c2020-06-29T13:05:52ZMichal Nowak[v9_11] Drop "#define activeemtpynode activeemtpynode64" from lib/dns/rbtdb.cc18dd943dab2124f2c04289fe164930455699334, among other things, renamed `activeemtpynode` to `activeemptynode`, but it seem that the `lib/dns/rbtdb.c:148:#define activeemtpynode activeemtpynode64` was kept (but it shouldn't?).c18dd943dab2124f2c04289fe164930455699334, among other things, renamed `activeemtpynode` to `activeemptynode`, but it seem that the `lib/dns/rbtdb.c:148:#define activeemtpynode activeemtpynode64` was kept (but it shouldn't?).July 2020 (9.11.21, 9.11.21-S1, 9.16.5, 9.17.3)Evan HuntEvan Hunthttps://gitlab.isc.org/isc-projects/bind9/-/issues/1898'.rst' files should be independent of configure option.2020-06-29T13:33:15ZMark Andrews'.rst' files should be independent of configure option.'.rst' files are being generated from doc/misc/options which has different line breaks depending upon which configure options are set as ' // not configured' differs. This impacts on the generated '.rst' files leading to churn in them. ...'.rst' files are being generated from doc/misc/options which has different line breaks depending upon which configure options are set as ' // not configured' differs. This impacts on the generated '.rst' files leading to churn in them. The '.rst' files are nominally independent of configure options.July 2020 (9.11.21, 9.11.21-S1, 9.16.5, 9.17.3)https://gitlab.isc.org/isc-projects/bind9/-/issues/894Update DNSSEC Guide2020-07-01T12:09:35ZStephen MorrisUpdate DNSSEC GuideThe current DNSSEC guide needs updating.
(Action from internal BIND Outreach meeting.)The current DNSSEC guide needs updating.
(Action from internal BIND Outreach meeting.)July 2020 (9.11.21, 9.11.21-S1, 9.16.5, 9.17.3)