ISC Open Source Projects issueshttps://gitlab.isc.org/groups/isc-projects/-/issues2020-08-13T13:13:31Zhttps://gitlab.isc.org/isc-projects/stork/-/issues/282Make notification that the DHCPv6 and DDNS are not configured less alarming (...2020-08-13T13:13:31ZVicky Riskvicky@isc.orgMake notification that the DHCPv6 and DDNS are not configured less alarming (machines page)The RED X for services that the CA is looking for that it doesn’t find has got to go. It is very alarming. This is not a real error condition, but it appears like a very critical fault.
Please replace with blue (preferred) or yellow co...The RED X for services that the CA is looking for that it doesn’t find has got to go. It is very alarming. This is not a real error condition, but it appears like a very critical fault.
Please replace with blue (preferred) or yellow color, and a ? or - or (i) or some other icon? (I don't know what icons are available to us, but I would be a happy to pick a better one if you would share the options.)
![Screen_Shot_2020-05-26_at_10.22.16_AM](/uploads/fa09cec08323aa23e6ae53a2b63bb4cc/Screen_Shot_2020-05-26_at_10.22.16_AM.png)
**UPDATE**: Two places has been already updated by Marcin: the "not detected at startup" services are shown as grey no-entry icons. However, there's third place where it still shows as red stop sign. It's the machines page.0.10https://gitlab.isc.org/isc-projects/stork/-/issues/281Edit mouseover on Stork logo2020-06-09T15:24:29ZVicky Riskvicky@isc.orgEdit mouseover on Stork logoWhile it is fine to have the dashboard linked to the Stork logo, but why doesn’t it say that in the mouseover on the logo? Edit the mouseover which now has some other stuff to say something like 'click for DHCP dashboard'While it is fine to have the dashboard linked to the Stork logo, but why doesn’t it say that in the mouseover on the logo? Edit the mouseover which now has some other stuff to say something like 'click for DHCP dashboard'https://gitlab.isc.org/isc-projects/stork/-/issues/280Add explicit link for Dashboard2020-07-13T17:15:44ZVicky Riskvicky@isc.orgAdd explicit link for DashboardWe need an explicit menu item that is Dashboard.
This could be a standalone menu item, or under the DHCP menu. We need an explicit menu item that is Dashboard.
This could be a standalone menu item, or under the DHCP menu. 0.10Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/stork/-/issues/279Please move 'machines' link to the 'configuration' menu2020-09-01T20:49:15ZVicky Riskvicky@isc.orgPlease move 'machines' link to the 'configuration' menuThe main purpose of the current 'machines' page is to add or remove machines from the list of machines to be monitored. It is more natural to keep this function under the 'configuration' menu. We then don't need the 'services' menu unles...The main purpose of the current 'machines' page is to add or remove machines from the list of machines to be monitored. It is more natural to keep this function under the 'configuration' menu. We then don't need the 'services' menu unless there are multiple services (e.g. DNS and DHCP) being monitored.1.0-backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/278Feedback from user UI review2021-03-05T13:33:44ZVicky Riskvicky@isc.orgFeedback from user UI reviewI spent about 2 hours going through the Stork UI with Cathy, prompting her to look for things and asking where she expected to find them. I will open separate issues for the things I think should be changed. I do have a (local) recording...I spent about 2 hours going through the Stork UI with Cathy, prompting her to look for things and asking where she expected to find them. I will open separate issues for the things I think should be changed. I do have a (local) recording of the whole session.
* [x] Move machines to the configuration menu. Cathy expected to configure machines to monitor under configuration. The initial dialog in the unconfigured system is good, but for later use, it is more natural to update the Stork configuration under the Configuration menu. #279
* [x] Cannot find the dashboard, which should be the main screen, the home screen. Add the first item under the Kea DHCP menu item = "Dashboard", or "DHCP Dashboard" #280
* [x] While it is fine to have the dashboard linked to the Stork logo, but why doesn’t it say that in the mouseover on the logo? Edit the mouseover which now has some other stuff. #281
* [ ] While we get that Stork is looking at app IDs, admins are looking for host names or IP addresses. Add a machines list with host IP at the bottom of the dashboard and you don't need the current machines page, except to configure new machines. #288
* [x] The RED ! for services that the CA is looking for that it doesn’t find has got to go. It is very alarming. Please replace with blue or yellow color, and a ? or - or (i) or some other icon? (I don't know what icons are available to us, but I would be a happy to pick a better one if you would share the options.) #282
* [x] Tables with lines are easier to read than the unlined tables on the dashboard page. If it doesn’t take up too much real estate, could we have line separators in the tables on the dashboard? #293
* [x] Cathy tried the button to rename a host on the machines page. This is there presumably in case of a typo in the host name. The problem is, changing the host name doesn’t clear out previously fetched info in buffer. This seems like a bug. #283
* [x] On the machines details page, on the right there is a button for details on the apps. Why not put more of the details right on there? At least, please put the status. There is plenty of unused screen real estate. The red ! is alarming, but Cathy couldn't tell what the problem was it was alerting her to. #284, #285
* [x] On the dashboard page, we need either better titles or mouseover that says it is showing you the top 5 ordered by utilization, something like that. Cathy couldn't tell why it was displaying those subnets and it was frustrating. #289
* [ ] Feature request for a button to save everything in stork to a file to send to ISC support. #290
observations without issues (yet)
* [ ] *Cathy eventually figured out that hitting return would refresh the screen, but it took a while to figure that out. Can we add a REFRESH button on that screen? (machines?)* - need screen shot for this don't see it.
* Cathy asked how can she configure the thresholds for alerts on pool utilization - this feature request already exists.
* Cathy couldn't find the link to the graphs, and didn't know she had't configured the address for Grafana.
* [ ] When you ask for a table to be displayed as say 30 rows, can it remember that info and display it that way every time? Cathy had to keep resetting the table length. #506.
* It could be an artifact of the demo set up- but there are some panels where you expect to see machine IP address and instead you get either appid (which is not that obvious or useful to the user as hostname) or hostname and no IP
* [x] Feature request - Cathy immediately started looking for the application logs.1.0-backloghttps://gitlab.isc.org/isc-projects/bind9/-/issues/1881Text edits in dnssec.rst2020-06-08T10:16:03ZSuzanne GoldlustText edits in dnssec.rstVarious text edits neededVarious text edits neededJune 2020 (9.11.20, 9.11.20-S1, 9.16.4, 9.17.2)Suzanne GoldlustSuzanne Goldlusthttps://gitlab.isc.org/isc-projects/bind9/-/issues/1880Implement distcheck2023-07-25T18:46:26ZMichal NowakImplement distcheck`make distcheck` does not pass on `master` (not even with https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/3527 applied):
- [x] system test fails because of read-only directories in the tarball
- [x] system test fails all over...`make distcheck` does not pass on `master` (not even with https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/3527 applied):
- [x] system test fails because of read-only directories in the tarball
- [x] system test fails all over the place
- [x] `lib/dns/tests` unit tests are not being executed (https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/3527#note_134700)
- [x] some unit tests fail (`file_test`)August 2023 (9.16.43, 9.16.43-S1, 9.18.18, 9.18.18-S1, 9.19.16)Michal NowakMichal Nowakhttps://gitlab.isc.org/isc-projects/bind9/-/issues/1877Reduce default for max-stale-ttl to something more reasonable - 12 hours or s...2022-05-19T11:42:16ZCathy AlmondReduce default for max-stale-ttl to something more reasonable - 12 hours or similarPer [Support ticket #16297](https://support.isc.org/Ticket/Display.html?id=16297), it was a surprise to find that despite having set `stale-answer-enable no;` in options, that cache was full of expired stale answer candidates that persis...Per [Support ticket #16297](https://support.isc.org/Ticket/Display.html?id=16297), it was a surprise to find that despite having set `stale-answer-enable no;` in options, that cache was full of expired stale answer candidates that persisted for up to 1 week.
It turns out that the default value for max-stale-ttl is 1 week.
The reason for instructing the cache to keep expired content, even if the serve-stale feature is not enabled is a good one - you don't know you want it until it's gone (and there's a problem out on the Interwebs ...). So in the interests of being able to recover in an emergency, and to use `rndc serve-stale on`, we keep stale content around just in case.
But 1 week is excessively long - that's effectively doubling the default max-cache-ttl
Generally most authoritative server issues like this are reported and fixed within a half day - which is also long enough for resolver admins to realise that something is broken and to enable serve-stale as a remedial action. (Although see also #1712 )June 2020 (9.11.20, 9.11.20-S1, 9.16.4, 9.17.2)https://gitlab.isc.org/isc-projects/bind9/-/issues/1876kasp: algnum migration test does not wait long enough.2020-06-29T14:04:33ZMark Andrewskasp: algnum migration test does not wait long enough.Job [#903691](https://gitlab.isc.org/isc-projects/bind9/-/jobs/903691) failed for 79790edb84f0d37dfa3d8d302925cdb7eac7ae12:
The zone is still in the process of being signed when the checks where performed.
```
I:kasp:check keys are cre...Job [#903691](https://gitlab.isc.org/isc-projects/bind9/-/jobs/903691) failed for 79790edb84f0d37dfa3d8d302925cdb7eac7ae12:
The zone is still in the process of being signed when the checks where performed.
```
I:kasp:check keys are created for zone migrate-nomatch-algnum.kasp (631)
I:kasp:check number of keys for zone migrate-nomatch-algnum.kasp in dir ns6 (632)
I:kasp:check key id 04654
I:kasp:check key id 09798
I:kasp:check key id 04373
I:kasp:check key id 22984
I:kasp:KEY1 ID 22984
I:kasp:KEY2 ID 9798
I:kasp:KEY3 ID 4654
I:kasp:KEY4 ID 4373
I:kasp:check DNSKEY rrset is signed correctly for zone migrate-nomatch-algnum.kasp (633)
I:kasp:check SOA rrset is signed correctly for zone migrate-nomatch-algnum.kasp (634)
I:kasp:check CDS and CDNSKEY rrset are signed correctly for zone migrate-nomatch-algnum.kasp (635)
I:kasp:check A a.migrate-nomatch-algnum.kasp rrset is signed correctly for zone migrate-nomatch-algnum.kasp (636)
I:kasp:error: A RRset not signed with key 4373
I:kasp:failed
I:kasp:dnssec-verify zone migrate-nomatch-algnum.kasp (637)
No correct ECDSAP256SHA256 signature for migrate-nomatch-algnum.kasp NS
No correct ECDSAP256SHA256 signature for migrate-nomatch-algnum.kasp NSEC
No correct ECDSAP256SHA256 signature for a.migrate-nomatch-algnum.kasp A
No correct ECDSAP256SHA256 signature for a.migrate-nomatch-algnum.kasp NSEC
No correct ECDSAP256SHA256 signature for b.migrate-nomatch-algnum.kasp A
No correct ECDSAP256SHA256 signature for b.migrate-nomatch-algnum.kasp NSEC
No correct ECDSAP256SHA256 signature for c.migrate-nomatch-algnum.kasp A
No correct ECDSAP256SHA256 signature for c.migrate-nomatch-algnum.kasp NSEC
No correct ECDSAP256SHA256 signature for ns6.migrate-nomatch-algnum.kasp A
No correct ECDSAP256SHA256 signature for ns6.migrate-nomatch-algnum.kasp NSEC
I:kasp:error: dnssec verify zone migrate-nomatch-algnum.kasp failed
I:kasp:failed
```
```
[beetle:bin/tests/system] marka% more kasp/*636
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62626
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 4096
; COOKIE: 539b5c354526c809010000005ecc56840b1cefd068a5ccb2 (good)
;; QUESTION SECTION:
;a.migrate-nomatch-algnum.kasp. IN A
;; ANSWER SECTION:
a.migrate-nomatch-algnum.kasp. 300 IN A 10.0.0.1
a.migrate-nomatch-algnum.kasp. 300 IN RRSIG A 5 3 300 20200608233541 20200525223541 9798 migrate-nomatch-algnum.kasp. p4xB5lIEIpu4pnIwLYUQOWKP7pVwcWNoQDQ9pEapzf820XpxCHpTDhmi 8VJ3HARLm5UdUgL6UBE/JQWXUfkbV9ZCYmbdNt6Y2CEltU7FSPyV5K15 8V7geR2JSHhQJ5jUFvrTGUhgkUCakYpJ+mIwrN0TknrUyGznaf6ohOTJ jTk=
[beetle:bin/tests/system] marka%
```
```
[beetle:bin/tests/system] marka% more kasp/*637
migrate-nomatch-algnum.kasp. 300 IN SOA mname1. . 3 20 20 1814400 3600
migrate-nomatch-algnum.kasp. 300 IN RRSIG SOA 5 2 300 20200608233635 20200525223635 9798 migrate-nomatch-algnum.kasp. bhgTCazJtBIrZDTTTCKRhkOF9lvmiE4TLIPmiDIx8xlynhCDvx/rL0nq h0LpaB7W8chi85ElE6rSDKkbrwyOjqYXP0OZJL+9zdFkgVBbrl51/rqQ XcqqcvclpOLb1XFdDxffVQui/KEsMPFB1gE0Sfb1eYNCrirE9ZVC7V9w D74=
migrate-nomatch-algnum.kasp. 300 IN RRSIG SOA 13 2 300 20200608233635 20200525223635 4373 migrate-nomatch-algnum.kasp. MfGPTKg4OHsLBwoE5Q10ir0Z/hK3gK15kJ8v0AhrTb0ZuM6o+S3wJ/ht tdOeII7+t0ntjj+p8/yFcZW9MN1ZGw==
migrate-nomatch-algnum.kasp. 300 IN NS ns6.migrate-nomatch-algnum.kasp.
migrate-nomatch-algnum.kasp. 300 IN RRSIG NS 5 2 300 20200608233541 20200525223541 9798 migrate-nomatch-algnum.kasp. b4O+//W02SIsTtsympGQmqkCnXOK02G4W3rczloBJeFa9MgNoYuJH+2H F5zA4e2MvG2JhklScavqU4IKtFP0STHZU83dP5Yx/JYk8PYbxrs94hfF OOxtQOxkxtTGBeEFBKgX/Z1YoFh+m4rkf5JLxg5QgGcGvMmIwtsxJxx5 X4I=
migrate-nomatch-algnum.kasp. 3600 IN NSEC a.migrate-nomatch-algnum.kasp. NS SOA RRSIG NSEC DNSKEY CDS CDNSKEY TYPE65534
migrate-nomatch-algnum.kasp. 3600 IN RRSIG NSEC 5 2 3600 20200608233541 20200525223541 9798 migrate-nomatch-algnum.kasp. u5n7aAdoruD3yBZnJUKPagjMGV+CKmZQGaudGjquseku0UqQO+G4rEl7 J9L4hvqPiv67sqHNzSjpf0AsxbbUxIzATqlOiC2H5Ib0NGsV3ZjXqwgV u98VtOkAk7IC8TlVoFfMeUukb03pZJv7rlrmnEUhIysaGQrmm2PuRQQi /40=
migrate-nomatch-algnum.kasp. 300 IN DNSKEY 257 3 5 AwEAAez6IqlwOH2xuvuqfL4WAEzoxkja0SM8b2PJ2/zCtyRZGIbkFRut Cqfk3i16aBYN3q1+VyeG9C1Tl+7CE0EpgLdw96FQFttpDZqvi6hiDewE EkSnCeI5WjydqtYfHvHp4wa53Re71x1Zy0jMJG6BZ5gYXBVrerrHsZDK pHaGcGNejYqpgGde1l9d6ALXYHeHxxaaafKi4SEWY2OX/x+Teawpl0gg jMPdboZy23oW1mRjMHmfVhuKZcpp5j/WoZkNzVaJgzbraGqMSM89Q9qm m6w6ap0yl9YtovB/SfBKVWSFnHmlYAU7mXG9RfHM6F6rhBqly0k6qj3t Kd4AwUIrfOE=
migrate-nomatch-algnum.kasp. 300 IN DNSKEY 256 3 5 AwEAAb4FGL/9IJ0rv3vMeTDHXVifDAoJy44JHtsgDHZjm9zzI9dzQy6c 0ePw6LqX5u3n7G9RJmpwllCzhZPbSx44KELvj9oJ7RjcfN1O5eYKhOlx kYhKOXJ+2NQT3kVodQAPWUHuJGGFtCajQ85aoWzwsXvz3LIDu8kw2U9V /4+Qh01X
migrate-nomatch-algnum.kasp. 300 IN DNSKEY 257 3 13 X4Mh8goXFmaZxyikplqOFJ/W4ANHtzBFYwtDkpcFaLMc4wKkt802UEKm bHzPeDPTiUv8twOccmmNu0OzEzg2YQ==
migrate-nomatch-algnum.kasp. 300 IN DNSKEY 256 3 13 HAGrXYKNr/iIxYopX13vedH36i5ufQk7Z8Kn6xSbdiz0JRcKPJitNiCp zHGKFwnFxHK6D8Q5PA2d1eePsku2lg==
migrate-nomatch-algnum.kasp. 300 IN RRSIG DNSKEY 5 2 300 20200608233635 20200525223635 22984 migrate-nomatch-algnum.kasp. uN2ku7GN1IDSeAv620XoDaZIQhciPVo5sl9InrigNP6Cmub4grZYSx+U VP9PmA2c9BrghLHenD3rsOVV5Sz5Q/ZIA9z2SDRA5n3i52x2AjJI+hSU nBLkBuQu5Knzaxv3EuBaUtBJ/AghspRLQb4atWalLLmDc0D56SoCygfJ xBES9dDD3uBTa9dO2tZHG2RpPE+CkATHmN2IhLyusL9KNWk3RxW1fFsQ Ag06ydkzGYJN2xGSMsuqruk+seqjzpHMq7X2Jnq6KpkHqvU8SjGOUi/1 kGPAuU70FOwy3fH7KeoNELAJmPVrXQMKvt9FiIPm+LwR1o6sO3nGLIq6 ZsahSQ==
migrate-nomatch-algnum.kasp. 300 IN RRSIG DNSKEY 13 2 300 20200608233635 20200525223635 4654 migrate-nomatch-algnum.kasp. nKRLpFysVhkzMoocVeXwri7nS+LGBrGF93ZRN3MOtOFGn1B9cBKVJPY1 wRP3mB8vmZhruRD8ZdBypUBuWhuncw==
migrate-nomatch-algnum.kasp. 300 IN CDS 22984 5 2 6D4521712D7213ED09B33FA79CE8ED7D1E666250476094DAAE13BD0B BCB063DC
migrate-nomatch-algnum.kasp. 300 IN RRSIG CDS 5 2 300 20200608233635 20200525223635 22984 migrate-nomatch-algnum.kasp. k3NsKuWgJrvNt9peaH/h1IwonvHSBQy7KOLm9wwYzZPBUfzTzzVbSoK5 9fIec4VfAs/KsXyVWtKca9ye6rgukJ8xKAin7ZpPStQhAcY1YnyxW6Sa kX/NmiP54pT7uNynCr44XfiEEGaVygtybW1pu/f9e33zhISJZMd+SnkS MnxJE/Q++RpxJXvO/Vam8ZQ6bK8+RHUAfPnFU5DsxCaPEyAgj8GKThbX tshmK3vdwWmTF5AVQr7tY7Go+uujAvJ7SjnsAnAAzjw1SzOaniUM+E2p m8UtSGqCoLxgfS5+cQ0yyv6JkXMXedgQES2T1e+Why02BTabeyVWn0O0 HbG9Aw==
migrate-nomatch-algnum.kasp. 300 IN RRSIG CDS 13 2 300 20200608233635 20200525223635 4654 migrate-nomatch-algnum.kasp. Ei3LUYsV/BsYmn7VnzhcLC0k4gnK+Viojkttsw0luJ7czYTQ2xXcuvuG 69oSPYq/VPXaMOgwEgw1UiD2FYRTbg==
migrate-nomatch-algnum.kasp. 300 IN CDNSKEY 257 3 5 AwEAAez6IqlwOH2xuvuqfL4WAEzoxkja0SM8b2PJ2/zCtyRZGIbkFRut Cqfk3i16aBYN3q1+VyeG9C1Tl+7CE0EpgLdw96FQFttpDZqvi6hiDewE EkSnCeI5WjydqtYfHvHp4wa53Re71x1Zy0jMJG6BZ5gYXBVrerrHsZDK pHaGcGNejYqpgGde1l9d6ALXYHeHxxaaafKi4SEWY2OX/x+Teawpl0gg jMPdboZy23oW1mRjMHmfVhuKZcpp5j/WoZkNzVaJgzbraGqMSM89Q9qm m6w6ap0yl9YtovB/SfBKVWSFnHmlYAU7mXG9RfHM6F6rhBqly0k6qj3t Kd4AwUIrfOE=
migrate-nomatch-algnum.kasp. 300 IN RRSIG CDNSKEY 5 2 300 20200608233635 20200525223635 22984 migrate-nomatch-algnum.kasp. vDldVbG+ppZ92B/YGLycx89gvXFqwq97tsGaFNl1OCTy9lUAcHMGZxsL 8PYBVwcjS7Nwx+L/LzjAFQz6CwD0PdeMBYzEWtgM4Nwws/fAWs03CYgW lAMLEccTE/3I/OCjWJHqe3BhGmXvuVFKMf4yXyJt9vEtkLO9203bZu88 PU6wUyu6+pro6a08I5dSfz1r4eOe+BgkLS5/RoNEo0Q+DxNjE6L/GuM3 MQFqxbRQwWYHP9y/k0Ph+T6ft7QSDhuezGJWahs12xMHVt0cR/ELMYBN 6PaDkZ2tIqwYOR/l5G6rydJm7VX9xKouAmsd4giwrv5xWilJ/CT5ztOo cGwwIg==
migrate-nomatch-algnum.kasp. 300 IN RRSIG CDNSKEY 13 2 300 20200608233635 20200525223635 4654 migrate-nomatch-algnum.kasp. 7XbjFGYsyy/UzO1KpcYgKs8zpch2r6sZwlErwBjqegrpFMpP1LEay35a hKHuiAg+IaJhINSZnIRcaWN7uQHedA==
migrate-nomatch-algnum.kasp. 0 IN TYPE65534 \# 5 0526460001
migrate-nomatch-algnum.kasp. 0 IN TYPE65534 \# 5 0559C80001
migrate-nomatch-algnum.kasp. 0 IN TYPE65534 \# 5 0D122E0000
migrate-nomatch-algnum.kasp. 0 IN TYPE65534 \# 5 0D11150000
migrate-nomatch-algnum.kasp. 0 IN RRSIG TYPE65534 5 2 0 20200608233635 20200525223635 9798 migrate-nomatch-algnum.kasp. jq0fW1YMv2N8NrMdtVikL7D5cm+YiN0qPRgy0MYcflcHr0dQW9JGpjDw ZQdbvat0WMeYdWneCc+SBR1va1V0agS0EZxYsbd54+3ZMy9u/ICiBVof BmsVMciHfLDXidPYBz3M6ROdEYjMQlNBBaq7MjCP2jF4qEob9rzY4MEH dOM=
migrate-nomatch-algnum.kasp. 0 IN RRSIG TYPE65534 13 2 0 20200608233635 20200525223635 4373 migrate-nomatch-algnum.kasp. n2dBdtTsCcF3nNXoABZUW1pEyPnqNM3z9OcrcE4dTN/LMsHK/qjNrowp sMw9YuOPTSFfV3FVoXwDteaCE1io9Q==
a.migrate-nomatch-algnum.kasp. 300 IN A 10.0.0.1
a.migrate-nomatch-algnum.kasp. 300 IN RRSIG A 5 3 300 20200608233541 20200525223541 9798 migrate-nomatch-algnum.kasp. p4xB5lIEIpu4pnIwLYUQOWKP7pVwcWNoQDQ9pEapzf820XpxCHpTDhmi 8VJ3HARLm5UdUgL6UBE/JQWXUfkbV9ZCYmbdNt6Y2CEltU7FSPyV5K15 8V7geR2JSHhQJ5jUFvrTGUhgkUCakYpJ+mIwrN0TknrUyGznaf6ohOTJ jTk=
a.migrate-nomatch-algnum.kasp. 3600 IN NSEC b.migrate-nomatch-algnum.kasp. A RRSIG NSEC
a.migrate-nomatch-algnum.kasp. 3600 IN RRSIG NSEC 5 3 3600 20200608233541 20200525223541 9798 migrate-nomatch-algnum.kasp. d1SyyU0E66w3ZkMHi6Oo5g8K9sA3iLUijRhZl43RrhadaC0P/Bp3a6sy HrG3lONvIvNsikd0jFluRz9ktc50v/ik1w+DcXrvRBxilttsxKOaLuiz Yp2An5zXnRLFYSU47VgOMMHOTaRMIoVM2GO9g89S5K7xerUn4Shrtg01 OAc=
b.migrate-nomatch-algnum.kasp. 300 IN A 10.0.0.2
b.migrate-nomatch-algnum.kasp. 300 IN RRSIG A 5 3 300 20200608233541 20200525223541 9798 migrate-nomatch-algnum.kasp. jrtEKm1y9DWHaZJSE0BrZt0jVXGbgyr9B5mFBuPmRB6BjgEFrWc4yHAE Zx7NzGvNLVHSUvPJcI2cGF9irvAqTdVFwwJVh0N8LQmGyeBAEE6toHi5 aJEQK0Aw4hkFnYk+cA06VTBTENUpDck6fIK9IxMD+Dlv0qqQlz8pYIh+ JRE=
b.migrate-nomatch-algnum.kasp. 3600 IN NSEC c.migrate-nomatch-algnum.kasp. A RRSIG NSEC
b.migrate-nomatch-algnum.kasp. 3600 IN RRSIG NSEC 5 3 3600 20200608233541 20200525223541 9798 migrate-nomatch-algnum.kasp. c4Z+8HKFj9MtPOq6S2JHbR000C/abBcCeW4fuoLIldhtonfqYREtUSKQ DhGtqzTT1PdWQxVyYzGxOst6Y/SBqz0lK0cqErFhK8KDBSgBjY/FpOYi pKWlcnA3jmUX4DP7SZqphhqXqJaVSr5US77C8smCqQBHme0ABjGDsE0V FXE=
c.migrate-nomatch-algnum.kasp. 300 IN A 10.0.0.3
c.migrate-nomatch-algnum.kasp. 300 IN RRSIG A 5 3 300 20200608233541 20200525223541 9798 migrate-nomatch-algnum.kasp. M+77iM5bJuRAtOUhR5klhcMmfOqAkPuxF/WSuJjA0iyTwkyFCyz3l50w H0D1FUTNOwt2GliBcnInNZ1L1bqATkDWhlPkUsRD0vw+vGMoFXd/QoeB mNpCZbiC1cRh2UFzgUqte4Onyl4ou4NgxhGJfOWpvESyse41zdnJdAdO cDk=
c.migrate-nomatch-algnum.kasp. 3600 IN NSEC ns6.migrate-nomatch-algnum.kasp. A RRSIG NSEC
c.migrate-nomatch-algnum.kasp. 3600 IN RRSIG NSEC 5 3 3600 20200608233541 20200525223541 9798 migrate-nomatch-algnum.kasp. CAR4zBq2fKuNwa/8POfP2X2pjbOD52Fg8czKQIWCwdS3vkp/HjYNZpAp 9ELpjHVuk+ejJLs0XcPeMfFqdYoMuaO1XhyFPciCoJAQlBtCAqdJ5DlZ HCH7vA6Er/Uts+uCJSFCZKRKNlxMRQXACBonJ/trxaxgSPgu87t7te1E KnU=
ns6.migrate-nomatch-algnum.kasp. 300 IN A 10.53.0.6
ns6.migrate-nomatch-algnum.kasp. 300 IN RRSIG A 5 3 300 20200608233541 20200525223541 9798 migrate-nomatch-algnum.kasp. f/4slXlwVmdghecejfLro3KWBX3iB9u8A+c1YHF1QyySqHQK8qh66nOd a2r7LRkWrMdQTkKmPfFMiuJd8sPxJOhNqGZYLeHmotP9zF9Wc6+ZfHp7 e2nDVr2tRULirx+LU5zqCnSIDFZjTbCJGkFa0pEEDOTiBwKDCc7+9ks4 p/g=
ns6.migrate-nomatch-algnum.kasp. 3600 IN NSEC migrate-nomatch-algnum.kasp. A RRSIG NSEC
ns6.migrate-nomatch-algnum.kasp. 3600 IN RRSIG NSEC 5 3 3600 20200608233541 20200525223541 9798 migrate-nomatch-algnum.kasp. jpLqpG3UfyKk9JDHdJh1fXSjYJn9lXztliIgdz/3WWvZohgS1vZNSgM8 J9Yj00bh/PbE9Y+7jwuT6QgCGwo2eh9tq8jI8fGj1CVxZuU7Co7wayh8 IBGJarVaCVZ1/CG1m85enCBljGW1WDEFadbHp5YUTCDO/nCkQTIal6XM 6zc=
migrate-nomatch-algnum.kasp. 300 IN SOA mname1. . 3 20 20 1814400 3600
[beetle:bin/tests/system] marka%
```July 2020 (9.11.21, 9.11.21-S1, 9.16.5, 9.17.3)Matthijs Mekkingmatthijs@isc.orgMatthijs Mekkingmatthijs@isc.orghttps://gitlab.isc.org/isc-projects/bind9/-/issues/1875KASP views: only one view started signing when policy was for both.2021-05-24T15:14:00ZMark AndrewsKASP views: only one view started signing when policy was for both.Job [#903708](https://gitlab.isc.org/isc-projects/bind9/-/jobs/903708) failed for 79790edb84f0d37dfa3d8d302925cdb7eac7ae12:
example.net was supposed to be signed in both views (example1 and example2) but only example2 succeeded in signi...Job [#903708](https://gitlab.isc.org/isc-projects/bind9/-/jobs/903708) failed for 79790edb84f0d37dfa3d8d302925cdb7eac7ae12:
example.net was supposed to be signed in both views (example1 and example2) but only example2 succeeded in signing example.net.
```
I:kasp:dnssec-verify zone override.none.unsigned (352)
I:kasp:wait for example.net to be signed (353)
I:kasp:error: wait for example.net to be signed failed
I:kasp:failed
I:kasp:check keys are created for zone example.net (354)
I:kasp:check number of keys for zone example.net in dir ns4 (355)
I:kasp:check key id 19778
I:kasp:KEY1 ID 19778
I:kasp:check DNSKEY rrset is signed correctly for zone example.net (356)
I:kasp:error: missing DNSKEY record in response for key 19778
I:kasp:error: DNSKEY RRset not signed with key 19778
I:kasp:error: DNSKEY RRset not signed with key 19778
I:kasp:failed
I:kasp:check SOA rrset is signed correctly for zone example.net (357)
I:kasp:error: SOA RRset not signed with key 19778
I:kasp:failed
I:kasp:check CDS and CDNSKEY rrset are signed correctly for zone example.net (358)
I:kasp:dnssec-verify zone example.net (359)
Zone contains no DNSSEC keys
I:kasp:error: dnssec verify zone example.net failed
I:kasp:failed
I:kasp:check TXT example.net (view example1) rrset is signed correctly (360)
I:kasp:error: TXT RRset not signed with key 19778
I:kasp:failed
I:kasp:wait for example.net to be signed (361)
```
```
set_zone "override.none.unsigned"
set_policy "test" "1" "3600"
set_server "ns5" "10.53.0.5"
TSIG="hmac-sha256:sha256:$SHA256"
wait_for_nsec
check_keys
check_apex
check_subdomain
dnssec_verify
set_zone "example.net"
set_server "ns4" "10.53.0.4"
TSIG="hmac-sha1:keyforview1:$VIEW1"
wait_for_nsec
check_keys
check_apex
dnssec_verify
n=$((n+1))
# check subdomain
echo_i "check TXT example.net (view example1) rrset is signed correctly ($n)"
ret=0
dig_with_opts "view.${ZONE}" "@${SERVER}" TXT > "dig.out.$DIR.test$n.txt" || log_error "dig view.${ZONE} TXT failed"
grep "status: NOERROR" "dig.out.$DIR.test$n.txt" > /dev/null || log_error "mismatch status in DNS response"
grep "view.${ZONE}\..*${DEFAULT_TTL}.*IN.*TXT.*view1" "dig.out.$DIR.test$n.txt" > /dev/null || log_error "missing view.${ZONE} TXT record in response"
check_signatures TXT "dig.out.$DIR.test$n.txt" "ZSK"
test "$ret" -eq 0 || echo_i "failed"
status=$((status+ret))
TSIG="hmac-sha1:keyforview2:$VIEW2"
wait_for_nsec
check_keys
check_apex
dnssec_verify
n=$((n+1))
# check subdomain
echo_i "check TXT example.net (view example2) rrset is signed correctly ($n)"
ret=0
dig_with_opts "view.${ZONE}" "@${SERVER}" TXT > "dig.out.$DIR.test$n.txt" || log_error "dig view.${ZONE} TXT failed"
grep "status: NOERROR" "dig.out.$DIR.test$n.txt" > /dev/null || log_error "mismatch status in DNS response"
grep "view.${ZONE}\..*${DEFAULT_TTL}.*IN.*TXT.*view2" "dig.out.$DIR.test$n.txt" > /dev/null || log_error "missing view.${ZONE} TXT record in response"
check_signatures TXT "dig.out.$DIR.test$n.txt" "ZSK"
test "$ret" -eq 0 || echo_i "failed"
status=$((status+ret))
```
```
25-May-2020 23:37:21.898 zone example.net/IN/example1: reconfiguring zone keys
25-May-2020 23:37:21.898 zone example.net/IN/example2: reconfiguring zone keys
25-May-2020 23:37:21.902 zone example.net/IN/example1: zone_rekey:dns_dnssec_findmatchingkeys failed: not found
25-May-2020 23:37:21.902 keymgr: keyring empty (zone example.net policy test)
25-May-2020 23:37:21.902 keymgr: no active key found for example.net (policy test)
25-May-2020 23:37:21.902 keymgr: DNSKEY example.net/ECDSAP384SHA384/19778 (CSK) created for policy test
25-May-2020 23:37:21.902 keymgr: examine CSK example.net/ECDSAP384SHA384/19778 type DNSKEY in state HIDDEN
25-May-2020 23:37:21.902 keymgr: can we transition CSK example.net/ECDSAP384SHA384/19778 type DNSKEY state HIDDEN to state RUMOURED?
25-May-2020 23:37:21.902 keymgr: dnssec evaluation of CSK example.net/ECDSAP384SHA384/19778 record DNSKEY: rule1=(~false or false) rule2=(~true or true) rule3=(~true or true)
25-May-2020 23:37:21.902 keymgr: transition CSK example.net/ECDSAP384SHA384/19778 type DNSKEY state HIDDEN to state RUMOURED!
25-May-2020 23:37:21.902 keymgr: examine CSK example.net/ECDSAP384SHA384/19778 type ZRRSIG in state HIDDEN
25-May-2020 23:37:21.902 keymgr: can we transition CSK example.net/ECDSAP384SHA384/19778 type ZRRSIG state HIDDEN to state RUMOURED?
25-May-2020 23:37:21.902 keymgr: dnssec evaluation of CSK example.net/ECDSAP384SHA384/19778 record ZRRSIG: rule1=(~false or false) rule2=(~true or true) rule3=(~true or true)
25-May-2020 23:37:21.902 keymgr: transition CSK example.net/ECDSAP384SHA384/19778 type ZRRSIG state HIDDEN to state RUMOURED!
25-May-2020 23:37:21.902 keymgr: examine CSK example.net/ECDSAP384SHA384/19778 type KRRSIG in state HIDDEN
25-May-2020 23:37:21.902 keymgr: can we transition CSK example.net/ECDSAP384SHA384/19778 type KRRSIG state HIDDEN to state RUMOURED?
25-May-2020 23:37:21.902 keymgr: dnssec evaluation of CSK example.net/ECDSAP384SHA384/19778 record KRRSIG: rule1=(~false or false) rule2=(~true or true) rule3=(~true or true)
25-May-2020 23:37:21.902 keymgr: transition CSK example.net/ECDSAP384SHA384/19778 type KRRSIG state HIDDEN to state RUMOURED!
25-May-2020 23:37:21.902 keymgr: examine CSK example.net/ECDSAP384SHA384/19778 type DS in state HIDDEN
25-May-2020 23:37:21.902 keymgr: can we transition CSK example.net/ECDSAP384SHA384/19778 type DS state HIDDEN to state RUMOURED?
25-May-2020 23:37:21.902 keymgr: policy says no to CSK example.net/ECDSAP384SHA384/19778 type DS state HIDDEN to state RUMOURED
25-May-2020 23:37:21.906 keymgr: examine CSK example.net/ECDSAP384SHA384/19778 type DNSKEY in state RUMOURED
25-May-2020 23:37:21.906 keymgr: can we transition CSK example.net/ECDSAP384SHA384/19778 type DNSKEY state RUMOURED to state OMNIPRESENT?
25-May-2020 23:37:21.906 keymgr: dnssec evaluation of CSK example.net/ECDSAP384SHA384/19778 record DNSKEY: rule1=(~false or false) rule2=(~true or true) rule3=(~true or true)
25-May-2020 23:37:21.906 keymgr: time says no to CSK example.net/ECDSAP384SHA384/19778 type DNSKEY state RUMOURED to state OMNIPRESENT (wait 7500 seconds)
25-May-2020 23:37:21.906 keymgr: examine CSK example.net/ECDSAP384SHA384/19778 type ZRRSIG in state RUMOURED
25-May-2020 23:37:21.906 keymgr: can we transition CSK example.net/ECDSAP384SHA384/19778 type ZRRSIG state RUMOURED to state OMNIPRESENT?
25-May-2020 23:37:21.906 keymgr: dnssec evaluation of CSK example.net/ECDSAP384SHA384/19778 record ZRRSIG: rule1=(~false or false) rule2=(~true or true) rule3=(~true or true)
25-May-2020 23:37:21.906 keymgr: time says no to CSK example.net/ECDSAP384SHA384/19778 type ZRRSIG state RUMOURED to state OMNIPRESENT (wait 90300 seconds)
25-May-2020 23:37:21.906 keymgr: examine CSK example.net/ECDSAP384SHA384/19778 type KRRSIG in state RUMOURED
25-May-2020 23:37:21.906 keymgr: can we transition CSK example.net/ECDSAP384SHA384/19778 type KRRSIG state RUMOURED to state OMNIPRESENT?
25-May-2020 23:37:21.906 keymgr: dnssec evaluation of CSK example.net/ECDSAP384SHA384/19778 record KRRSIG: rule1=(~false or false) rule2=(~true or true) rule3=(~true or true)
25-May-2020 23:37:21.906 keymgr: time says no to CSK example.net/ECDSAP384SHA384/19778 type KRRSIG state RUMOURED to state OMNIPRESENT (wait 7500 seconds)
25-May-2020 23:37:21.906 keymgr: examine CSK example.net/ECDSAP384SHA384/19778 type DS in state HIDDEN
25-May-2020 23:37:21.906 keymgr: can we transition CSK example.net/ECDSAP384SHA384/19778 type DS state HIDDEN to state RUMOURED?
25-May-2020 23:37:21.906 keymgr: policy says no to CSK example.net/ECDSAP384SHA384/19778 type DS state HIDDEN to state RUMOURED
25-May-2020 23:37:21.906 keymgr: keyring: dnskey example.net/ECDSAP384SHA384/19778 (policy test)
25-May-2020 23:37:21.906 keymgr: DNSKEY example.net/ECDSAP384SHA384/19778 (CSK) matches policy test
25-May-2020 23:37:21.906 keymgr: DNSKEY example.net/ECDSAP384SHA384/19778 (CSK) is active in policy test
25-May-2020 23:37:21.906 keymgr: examine CSK example.net/ECDSAP384SHA384/19778 type DNSKEY in state RUMOURED
25-May-2020 23:37:21.906 keymgr: can we transition CSK example.net/ECDSAP384SHA384/19778 type DNSKEY state RUMOURED to state OMNIPRESENT?
25-May-2020 23:37:21.906 keymgr: dnssec evaluation of CSK example.net/ECDSAP384SHA384/19778 record DNSKEY: rule1=(~false or false) rule2=(~true or true) rule3=(~true or true)
25-May-2020 23:37:21.906 keymgr: time says no to CSK example.net/ECDSAP384SHA384/19778 type DNSKEY state RUMOURED to state OMNIPRESENT (wait 7500 seconds)
25-May-2020 23:37:21.906 keymgr: examine CSK example.net/ECDSAP384SHA384/19778 type ZRRSIG in state RUMOURED
25-May-2020 23:37:21.906 keymgr: can we transition CSK example.net/ECDSAP384SHA384/19778 type ZRRSIG state RUMOURED to state OMNIPRESENT?
25-May-2020 23:37:21.906 keymgr: dnssec evaluation of CSK example.net/ECDSAP384SHA384/19778 record ZRRSIG: rule1=(~false or false) rule2=(~true or true) rule3=(~true or true)
25-May-2020 23:37:21.906 keymgr: time says no to CSK example.net/ECDSAP384SHA384/19778 type ZRRSIG state RUMOURED to state OMNIPRESENT (wait 90300 seconds)
25-May-2020 23:37:21.906 keymgr: examine CSK example.net/ECDSAP384SHA384/19778 type KRRSIG in state RUMOURED
25-May-2020 23:37:21.906 keymgr: can we transition CSK example.net/ECDSAP384SHA384/19778 type KRRSIG state RUMOURED to state OMNIPRESENT?
25-May-2020 23:37:21.906 keymgr: dnssec evaluation of CSK example.net/ECDSAP384SHA384/19778 record KRRSIG: rule1=(~false or false) rule2=(~true or true) rule3=(~true or true)
25-May-2020 23:37:21.906 keymgr: time says no to CSK example.net/ECDSAP384SHA384/19778 type KRRSIG state RUMOURED to state OMNIPRESENT (wait 7500 seconds)
25-May-2020 23:37:21.906 keymgr: examine CSK example.net/ECDSAP384SHA384/19778 type DS in state HIDDEN
25-May-2020 23:37:21.906 keymgr: can we transition CSK example.net/ECDSAP384SHA384/19778 type DS state HIDDEN to state RUMOURED?
25-May-2020 23:37:21.906 keymgr: policy says no to CSK example.net/ECDSAP384SHA384/19778 type DS state HIDDEN to state RUMOURED
[key read failure]
25-May-2020 23:37:21.906 dns_dnssec_findzonekeys2: error reading Kexample.net.+014+19778.private: end of file
25-May-2020 23:37:21.906 zone example.net/IN/example1: sign_apex:dns__zone_findkeys -> end of file
25-May-2020 23:37:21.906 zone_settimer: zone example.net/IN/example1: enter
25-May-2020 23:37:21.906 Fetching example.net/ECDSAP384SHA384/19778 (CSK) from key repository.
25-May-2020 23:37:21.906 DNSKEY example.net/ECDSAP384SHA384/19778 (CSK) is now published
25-May-2020 23:37:21.906 DNSKEY example.net/ECDSAP384SHA384/19778 (CSK) is now active
...
25-May-2020 23:37:21.918 zone_journal: zone example.net/IN/example2: enter
25-May-2020 23:37:21.918 journal file example2.db.jnl does not exist, creating it
25-May-2020 23:37:21.918 writing to journal
25-May-2020 23:37:21.918 del example.net. 300 IN SOA mname1. . 1 20 20 1814400 3600
25-May-2020 23:37:21.918 add example.net. 300 IN SOA mname1. . 2 20 20 1814400 3600
25-May-2020 23:37:21.918 add re-sign example.net. 3600 IN RRSIG DNSKEY 14 2 3600 20200608233721 20200525223721 19778 example.net. AHPN1pNiPLPBRrWHkKSSuD8eWKaqq7aFDQwynSoay+9dBxoGiI8BFhwR SQ8Uku5Y2jDwPn5nDuvN0Nvh7Omq+BiSUWhI+PRM/z0sglMi7RMxctC4 M+wJbsbI7YmAW1KT
25-May-2020 23:37:21.918 add re-sign example.net. 0 IN RRSIG TYPE65534 14 2 0 20200608233721 20200525223721 19778 example.net. 6Lk7Bkmme9tp1U5DSoNJ/2jyyujdmGeDEOdSjTSg81Ajmh3/k5Shz3UK QqrGZPLmJZ4I0q/UyiYt13CXQOPF3ZzXIeCB9TC4qkSvjWSuTSzHLPmF Rz9s68CtwKMCxhzW
25-May-2020 23:37:21.918 add re-sign example.net. 300 IN RRSIG SOA 14 2 300 20200608233721 20200525223721 19778 example.net. ZtWdbyf2mDjqd4ahChSQIZcY8fLJ2tPZqjUa1CQNrvn27sUVH5v6M2h0 tL2FDAiKOJiv0gUrMhOC87rxAkThaIOpAT/LG0oMEfvjXXu1UYzPaPAR F4mkKnQVPHEwJMLp
25-May-2020 23:37:21.918 add example.net. 3600 IN DNSKEY 257 3 14 TEEOTTNdzuL5C0AA1eGvZaMNPCGmTtRDNDVmbKws6JJ6G+kWd2bqVAWI Czc6Y3ni25L9dN34OBkAHkCh1NM5AoN+Jzp5HdNcRh9Nsw4mntNFu+3M H/qNn7IIhfwwM1vz
25-May-2020 23:37:21.918 add example.net. 0 IN TYPE65534 \# 5 0E4D420000
25-May-2020 23:37:22.318 zone_settimer: zone example.net/IN/example2: enter
25-May-2020 23:37:22.318 zone_settimer: zone example.net/IN/example2: enter
25-May-2020 23:37:22.318 zone_settimer: zone example.net/IN/example2: enter
25-May-2020 23:37:22.318 zone example.net/IN/example2: next key event in 7500 seconds
25-May-2020 23:37:22.318 zone example.net/IN/example2: next key event: 26-May-2020 01:42:21.898
25-May-2020 23:37:22.318 zone_settimer: zone example.net/IN/example2: enter
25-May-2020 23:37:22.318 zone_timer: zone example.net/IN/example2: enter
25-May-2020 23:37:22.318 zone_maintenance: zone example.net/IN/example2: enter
25-May-2020 23:37:22.318 zone_sign: zone example.net/IN/example2: enter
25-May-2020 23:37:22.338 zone_journal: zone example.net/IN/example2: enter
25-May-2020 23:37:22.338 writing to journal
25-May-2020 23:37:22.338 del example.net. 300 IN SOA mname1. . 2 20 20 1814400 3600
25-May-2020 23:37:22.338 del re-sign example.net. 0 IN RRSIG TYPE65534 14 2 0 20200608233721 20200525223721 19778 example.net. 6Lk7Bkmme9tp1U5DSoNJ/2jyyujdmGeDEOdSjTSg81Ajmh3/k5Shz3UK QqrGZPLmJZ4I0q/UyiYt13CXQOPF3ZzXIeCB9TC4qkSvjWSuTSzHLPmF Rz9s68CtwKMCxhzW
25-May-2020 23:37:22.338 del re-sign example.net. 300 IN RRSIG SOA 14 2 300 20200608233721 20200525223721 19778 example.net. ZtWdbyf2mDjqd4ahChSQIZcY8fLJ2tPZqjUa1CQNrvn27sUVH5v6M2h0 tL2FDAiKOJiv0gUrMhOC87rxAkThaIOpAT/LG0oMEfvjXXu1UYzPaPAR F4mkKnQVPHEwJMLp
25-May-2020 23:37:22.338 del example.net. 0 IN TYPE65534 \# 5 0E4D420000
25-May-2020 23:37:22.338 add example.net. 300 IN SOA mname1. . 3 20 20 1814400 3600
25-May-2020 23:37:22.338 add re-sign example.net. 300 IN RRSIG NS 14 2 300 20200606134700 20200525223722 19778 example.net. SxpQl+kWc3DaF1YzsaYmokBxvLZSjtTA3viYulQ98pSomLpJsEM9pA/r CZo2mlKvuUjBq5i3UpgV/Bo+MT6CrsvI1nzwb3VCA4viAoWaTGvqoVMm vtcx7dQdTnnhhCmP
25-May-2020 23:37:22.338 add re-sign ns4.example.net. 3600 IN RRSIG NSEC 14 3 3600 20200606134700 20200525223722 19778 example.net. 6nZD7wqpaUnHbnQwAS7WY0pPqr/LEpvkJtoDC2bdu/mVSSqhHkE8Bo63 CrTMAWAtdKQ9F02Eta6FNgjL1tXNJpd7FOBpR9HdrHZYgxxf6RqT1Cyq JvWSR2y97ga+MIPA
25-May-2020 23:37:22.338 add re-sign ns4.example.net. 300 IN RRSIG A 14 3 300 20200606134700 20200525223722 19778 example.net. 4wenD6hbHJoyzxcAmE3fML7pY/Uf+l9URT/lcZxSFXYbKuFsntFUaZdL Ot43v2VeKMaSQJ0WZbRVmWb6yAQOsmbrwiKIx7PheLAmajJxwO9v1Z7N MUSaL9/cE5Z6FU65
25-May-2020 23:37:22.338 add re-sign view.example.net. 3600 IN RRSIG NSEC 14 3 3600 20200606134700 20200525223722 19778 example.net. YVUwfqmUz9X0PLAcT0YWXe85vp1qp42pft+x24UM5zETrfVywXqZj1LJ GAswQILyaj8Nq9uH6JTIB20HIghjYaR5J4608xHov+wu4hs7YjoSFcWk +L5Zz1iYZPTouQmM
25-May-2020 23:37:22.338 add re-sign view.example.net. 300 IN RRSIG TXT 14 3 300 20200606134700 20200525223722 19778 example.net. EoRsqC/50MPHMc3yVCIB95Tty+uKXeQ96qq5DwvCs0jfhR0VRhYaMUk3 DI0CUCDD6k8tAYyj4WpDCTWSQoSFDB+YpYl5bA5ruX+g6Z6/EYRayMND jRE+7lBexK4PCRmT
25-May-2020 23:37:22.338 add re-sign example.net. 3600 IN RRSIG NSEC 14 2 3600 20200606134700 20200525223722 19778 example.net. vf4VJyOBQ+I2Isutgdz9sa4GdS7Lok9IfDnWsn6FqtG2Uk9zU1MFvnL2 8fvVr0VNu8SLBn9XbMNaOES0CMGbIsA5Chfz8oZmP30ut/2tSbr86d/G fdZeyFMWdMXPjKsy
25-May-2020 23:37:22.338 add re-sign example.net. 0 IN RRSIG TYPE65534 14 2 0 20200606134700 20200525223722 19778 example.net. SpkVjCbqdoiZU+HmbUyjXBebD2Nne4U0Gl6iOvi0rODseCI/ZVs803lv DcrtSKOJdVXHvImU4MnN5VylFi2OBsPqSlXNlnKXIl8v83QHoe+mUFqj 3j5/fO6B1PPXxjgn
25-May-2020 23:37:22.338 add re-sign example.net. 300 IN RRSIG SOA 14 2 300 20200608233722 20200525223722 19778 example.net. oP3xTp4arrw/3se2m1AYgzYk8YV66uahsvSxdqMM3YzVSXykPPeICbnP RNjmiiSYn47IvDCytgMzbvqGgsX+8dKNq5b/C5xLXBxjogdRW0uM4bU+ hnyYa+lujWTu+1Xb
25-May-2020 23:37:22.338 add ns4.example.net. 3600 IN NSEC view.example.net. A RRSIG NSEC
25-May-2020 23:37:22.338 add view.example.net. 3600 IN NSEC example.net. TXT RRSIG NSEC
25-May-2020 23:37:22.338 add example.net. 3600 IN NSEC ns4.example.net. NS SOA RRSIG NSEC DNSKEY TYPE65534
25-May-2020 23:37:22.338 add example.net. 0 IN TYPE65534 \# 5 0E4D420001
25-May-2020 23:37:22.766 zone_needdump: zone example.net/IN/example2: enter
...
25-May-2020 23:38:11.324 client @0x7f6fd8014ac0 10.53.0.1#38429: TCP request
25-May-2020 23:38:11.324 client @0x7f6fd8014ac0 10.53.0.1#38429: view example1: using view 'example1'
25-May-2020 23:38:11.324 client @0x7f6fd8014ac0 10.53.0.1#38429: view example1: request has valid signature: keyforview1
25-May-2020 23:38:11.324 client @0x7f6fd8014ac0 10.53.0.1#38429/key keyforview1: view example1: recursion not available
25-May-2020 23:38:11.324 query client=0x7f6fd8014ac0 thread=0x7f7011890700 (<unknown-query>): ns_query_start
25-May-2020 23:38:11.324 query client=0x7f6fd8014ac0 thread=0x7f7011890700 (example.net/NSEC): qctx_init
```June 2021 (9.11.33, 9.11.33-S1, 9.16.17/9.16.18, 9.16.17-S1/9.16.18-S1, 9.17.14/9.17.15)Matthijs Mekkingmatthijs@isc.orgMatthijs Mekkingmatthijs@isc.orghttps://gitlab.isc.org/isc-projects/kea/-/issues/1251unit test CommunicationStateTest.logFormatClockSkew fails sporadically2020-12-10T13:52:38ZMichal Nowikowskiunit test CommunicationStateTest.logFormatClockSkew fails sporadicallyJenkins Job with this UT failing:
https://jenkins.isc.org/job/kea-1.7/job/ut-thread/105/testReport/Jenkins Job with this UT failing:
https://jenkins.isc.org/job/kea-1.7/job/ut-thread/105/testReport/kea1.9.3Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/1250unit test RenewTest.renewWithExcludedPrefix fails sporadically2020-12-10T09:56:01ZMichal Nowikowskiunit test RenewTest.renewWithExcludedPrefix fails sporadicallyJenkins Job with this UT failing:
https://jenkins.isc.org/job/kea-1.7/job/ut-extended/206/testReport/Jenkins Job with this UT failing:
https://jenkins.isc.org/job/kea-1.7/job/ut-extended/206/testReport/kea1.9.3Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/bind9/-/issues/1873system test fails on single stack system2020-06-06T11:43:47ZPeter Daviessystem test fails on single stack systemsystem test fails on single stack system:
```
I:resolver:check that the resolver limits the number of NS records it follows in a referral response (28)
I:resolver:query count error: 1 NS records: expected queries 2, actual 1
I:resolver...system test fails on single stack system:
```
I:resolver:check that the resolver limits the number of NS records it follows in a referral response (28)
I:resolver:query count error: 1 NS records: expected queries 2, actual 1
I:resolver:query count error: 2 NS records: expected queries 4, actual 2
I:resolver:query count error: 3 NS records: expected queries 6, actual 3
I:resolver:query count error: 4 NS records: expected queries 8, actual 4
I:resolver:query count error: 5 NS records: expected queries 10, actual 5
I:resolver:query count error: 6 NS records: expected queries 10, actual 5
I:resolver:query count error: 7 NS records: expected queries 10, actual 5
I:resolver:query count error: 8 NS records: expected queries 10, actual 5
I:resolver:query count error: 9 NS records: expected queries 10, actual 5
I:resolver:query count error: 10 NS records: expected queries 10, actual 5
```
[RT #16496](https://support.isc.org/Ticket/Display.html?id=16496)June 2020 (9.11.20, 9.11.20-S1, 9.16.4, 9.17.2)https://gitlab.isc.org/isc-projects/kea/-/issues/1249changes for release 1.7.82020-05-25T10:12:20ZMichal Nowikowskichanges for release 1.7.8kea1.7.8Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/kea/-/issues/1248doc/sphinx/Makefile uses GNU make specific features2020-07-28T08:24:05ZFrancis Dupontdoc/sphinx/Makefile uses GNU make specific featuresThere are a few:
```
foo=$(shell xxx)
```
and
```
foo=$(foreach x,y,z)
```There are a few:
```
foo=$(shell xxx)
```
and
```
foo=$(foreach x,y,z)
```kea1.7.10Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/bind9/-/issues/1872Text edits in advanced.rst2020-06-08T10:15:58ZSuzanne GoldlustText edits in advanced.rstVarious content, clarity, and grammar edits neededVarious content, clarity, and grammar edits neededJune 2020 (9.11.20, 9.11.20-S1, 9.16.4, 9.17.2)Suzanne GoldlustSuzanne Goldlusthttps://gitlab.isc.org/isc-projects/bind9/-/issues/1871RNDC command to dump stats2023-05-31T11:52:38ZVicky Riskvicky@isc.orgRNDC command to dump statsWe have a request, from a resolver operator, to be able to issue an rndc command to dump a file of statistics in some format that can be imported and processed by Prometheus. I think the use case is, the node might be in a remote pop wit...We have a request, from a resolver operator, to be able to issue an rndc command to dump a file of statistics in some format that can be imported and processed by Prometheus. I think the use case is, the node might be in a remote pop with limited connectivity and setting up on-going streaming may be difficult for some reason, or perhaps there isn't the access for that.
entered on behalf of cmosher@quad9.netBIND 9.19.xhttps://gitlab.isc.org/isc-projects/kea/-/issues/1247race condition during configuration reading from db and setting to db2020-07-07T10:40:05ZMichal Nowikowskirace condition during configuration reading from db and setting to dbWhen there is a series of *-set commands executed during 1second it may appear that Kea starts reading modifications from the db in the middle of this second. So it will read only part of modifications. In next turn Kea checks timestamp ...When there is a series of *-set commands executed during 1second it may appear that Kea starts reading modifications from the db in the middle of this second. So it will read only part of modifications. In next turn Kea checks timestamp of modifications: ts > last_ts. Unfortunately timestamps have 1s resolution so the other part of changes will not be noticed as they happend in the same last_ts.
This can happen quite frequently when config-fetch-wait-time is set to 1s. In that case Kea checks modifications every second so there is high chance that it will get in the middle of series of modification.
It is exposed by Forge test: tests/dhcpv6/kea_only/config_backend/test_cb_v4_options.py::test_multiple_subnet_optionkea1.7.10Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/1246bump up libs and hooks versions before 1.7.82020-05-22T19:00:21ZMichal Nowikowskibump up libs and hooks versions before 1.7.8kea1.7.8Razvan BecheriuRazvan Becheriuhttps://gitlab.isc.org/isc-projects/bind9/-/issues/1870[Support#12071] [RT#46548] Output stale/expired data with 'rndc dumpdb'2022-07-18T19:24:42ZCathy Almond[Support#12071] [RT#46548] Output stale/expired data with 'rndc dumpdb'We want an option to dump, not just the stale/expired data, but the really really expired data.
The use case for this is that currently there is **still** no way to find out how much of cache is expired and awaiting clean-up without get...We want an option to dump, not just the stale/expired data, but the really really expired data.
The use case for this is that currently there is **still** no way to find out how much of cache is expired and awaiting clean-up without getting a core dump and analysing it. Feature request #101 tackles the stale case (for use by the serve-stale feature), but doesn't touch the fully-expired case.
Support (and customers) do, several times a year, encounter edge cases resolver query patterns instances where it appears that there are problems with caches holding on to expired RRsets for much longer than anticipated.
I do not think that this should be the default behaviour for rndc dumpdb -all - but an addition option -expired would make this content accessible to mere mortals as opposed to core dump analysts.October 2020 (9.11.24, 9.11.24-S1, 9.16.8, 9.16.8-S1, 9.17.6)Matthijs Mekkingmatthijs@isc.orgMatthijs Mekkingmatthijs@isc.org