Skip to content

`knotc zone-check` complains about missing zone file when using the `dnsproxy` module

Hey!

I'm playing with the dnsproxy knotd module and I can't seem to convince knotc zone-check that proxied zones don't need a zone file (even with the example from the documentation):

# vi: ts=2 sw=2 et:

server:
    rundir: "/run/knot"
    user: knot:knot
    automatic-acl: on
    listen: [ 127.0.0.1@53 ]

log:
  - target: syslog
    any: debug

database:
    storage: "/var/lib/knot"

remote:
   - id: hidden
     address: 1.1.1.1

mod-dnsproxy:
   - id: forward
     remote: hidden
     fallback: off

zone:
   - domain: example.com
     module: mod-dnsproxy/forward
# dig +short example.com
93.184.216.34
# knotc zone-check
error: [example.com.] failed to check zone file (not exists)
# journalctl -b -u knot.service -p info -o short-monotonic --no-hostname
...
[868919.867204] systemd[1]: Starting knot.service...
[868919.880164] knotc[2358390]: Configuration is valid
[868919.904823] knotd[2358393]: info: Knot DNS 3.3.1 starting
[868919.905080] knotd[2358393]: info: loaded configuration file '/etc/knot/knot.conf', mapsize 512 MiB
[868919.905135] knotd[2358393]: info: using UDP reuseport, incoming TCP Fast Open
[868919.905186] knotd[2358393]: info: binding to interface 127.0.0.1@53
[868919.908665] knotd[2358393]: info: loading 1 zones
[868919.908907] knotd[2358393]: info: [example.com.] zone will be loaded
[868919.909070] knotd[2358393]: info: starting server
[868919.909365] knotd[2358393]: error: [example.com.] failed to parse zone file '/var/lib/knot/example.com.zone' (not exists)
[868919.909437] knotd[2358393]: info: [example.com.] zone not found
[868919.909471] knotd[2358393]: error: [example.com.] zone event 'load' failed (not exists)
[868919.911882] knotd[2358393]: info: control, binding to '/run/knot/knot.sock'
[868919.911954] knotd[2358393]: info: server started in the foreground, PID 2358393
[868919.912183] systemd[1]: Started knot.service.

Is there any way to avoid this error, so I can still use zone-check to make sure the config is valid? This is with both 3.3.1 and 3.4.dev0+1704656692.81a57d9bf.