3 Říj
2025
3 Říj
'25
6:44
I would generally recommend avoiding frequent
`conf-set include`
commands, as include is quite inefficient.
Ok.
Knot doesn't have a good overview of which parts
of the configuration
are changed by the include.
What about something like:
# cat zones.txt
conf-set zone.domain example.com
conf-set zone.domain example.net
# /opt/knot/sbin/knotc -s /run/knot_dns/knot_dns.sock < zones.txt
Ah ok, that's interesting. We currently use the `include` syntax when mass setting up
a new knot instance with a lot of domains without having to make lots of separate
"calls" to `knotc`. But this seems an alternate approach to do the same thing
but without using `include. I'll look into this and compare it.
Of course the primary issue will be fixed.
Great, thanks!
Rob