Dear Knot developers,
Our Knot DNS systemd unit files do not currently have a "Type"
attribute, so it defaults to "simple". This works quite well. However,
we can set "Type" to one of "notify" or "notify-reload" for better
systemd integration.
For this, Knot DNS needs to support the READY=1, STOPPING=1, RELOADING=1
messages using sd_notify.
Could you please clarify which messages Knot DNS sends?
Regards,
Anand Buddhdev
RIPE NCC
Hello,
I see in the directory with zones and journal I see directories journal.<timestamp>.bak (same for keys and timers) and files journal.<timestamp>.export
time stamp and file date are the moment of upgrade from a knot compiled with lmdb0 to a knot compiled with lmdb1
Can I remove those files or directory ? (I suspect they are used during conversion of mdb files)
--
Erwan David
Since upgrade to knot 3.6, when I restart the knot server, a new serial is generated for the secondary zones,
putting them out of sync with the primary.
Logs in 3.5
Aug 25 10:31:50 ns knot[45038]: info: [domain.] zone will be loaded
Aug 25 10:31:51 ns knot[45038]: info: [domain.] zone loaded from journal, serial 2026023115
Aug 25 10:31:51 ns knot[45038]: info: [domain.] zone file loaded, serial updated 2026023115 -> 2026082500
Aug 25 10:31:51 ns knot[45038]: info: [domain.] loaded, serial none -> 2026082500 -> 2026023115, 21088 bytes, expires in 2137390 seconds
Last line show the serial is set back to the serial of the journal loaded zone
When starting 3.6
Sep 24 07:49:14 ns knot[23114]: info: [domain.] zone will be loaded
Sep 24 07:49:14 ns knot[23114]: info: [domain.] zone loaded from journal, serial 2026023175
Sep 24 07:49:14 ns knot[23114]: info: [domain.] zone file loaded, serial updated 2026023175 -> 2026092400
Sep 24 07:49:14 ns knot[23114]: info: [domain.] loaded, serial none -> 2026092400, 21088 bytes, expires in 2158298 seconds
The serial is not set back to the serail from the journal. As you can see in this case the primary does not use a date based serial number,
thus the secondary is then out of sync and refuses the notifications
--
Erwan David
knotd still fails to start if it can't load certificates or keys. This
appears to be a bug given that "knotd: server crashes when it fails to
load a QUIC/TLS key" is in the release notes for knot-dns v3.5.6.
Below is a patch that allows the server to start if knotd can't load the
certificates/keys.
---
src/knot/server/server.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/src/knot/server/server.c b/src/knot/server/server.c
index 8de6f1a8f..e03178144 100644
--- a/src/knot/server/server.c
+++ b/src/knot/server/server.c
@@ -824,9 +824,10 @@ static int configure_sockets(conf_t *conf, server_t *s)
s->quic_active = conf->cache.xdp_quic > 0 || convent_quic > 0 ||
quic_rmt_count(conf, C_QUIC) > 0;
s->tls_active = convent_tls > 0 || quic_rmt_count(conf, C_TLS) > 0;
if (s->quic_active || s->tls_active) {
- if (init_creds(conf, s) != KNOT_EOK) {
- server_deinit_iface_list(newlist, nifs);
- return KNOT_ERROR;
+ int ret;
+ if ((ret = init_creds(conf, s)) != KNOT_EOK) {
+ log_error("failed to configure server credentials (%s)",
+ knot_strerror(ret));
}
}
--
2.54.0
deb13
knot 3.5.6
prometheus 2.53.3+ds1-2
grafana 13.0.2
i am running the [python version](https://gitlab.nic.cz/knot/knot-dns/-/tree/master/python/knot_exporter)
of knot_exporter on the dns server
.../knot-exporter --web-listen-addr 666.42.7.11 --web-listen-port 9443
prometheus on my webby host seems to be pulling happily from 9443 of the
knotty server. i.e. http://knotty.host:9443/metrics has a lot of data
and http://webby.host:9090/metrics has data
and grafana drilldown/metrics has pretty data
but which main grafana dashboard json should i be using for knot?
https://grafana.com/grafana/dashboards/14989-knot-metrics-dashboard/
displays a lot of No Data
randy
