Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.
Ubuntu package 2.7.3-1~ubuntu18.04.1ppa1 contains no modules (e.g. mod-queryacl)
we are reviewing an alternative to our actuially running nameserver software.
Depending on the higher expectations to the new nameservice we would use, we give knot-dns a try.
Our company use largly ubuntu as building block of the infratructure, so we depend on ubuntu packages.
The ubunbu package version 2.7.3-1~ubuntu18.04.1ppa1 does not contain further modules like mod-queryacl for example.
Is that on purpose or are there technical reasons, like build problems, for the lack of the modules?
Greetings
Frank
Edited
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
Activity
Sort or filter
Newest first
Oldest first
Show all activity
Show comments only
Show history only
Ghost Userchanged title from Ubutu package 2.7.3-1~ubuntu18.04.1ppa1 contains no modules (e.g. mod-queryacl) to Ubuntu package 2.7.3-1~ubuntu18.04.1ppa1 contains no modules (e.g. mod-queryacl)
changed title from Ubutu package 2.7.3-1~ubuntu18.04.1ppa1 contains no modules (e.g. mod-queryacl) to Ubuntu package 2.7.3-1~ubuntu18.04.1ppa1 contains no modules (e.g. mod-queryacl)
yes, i've tried to configure the mod-queryacl module and got an error message:
root@f-dns1:~# knotc --force conf-import knotd.conf error: module, failed to open '/usr/lib/x86_64-linux-gnu/knot/query.so' (/usr/lib/x86_64-linux-gnu/knot/query.so: cannot open shared object file: No such file or directory)error: config, file 'knotd.conf', line 17, module 'mod-query' (not exists)error: import (not exists)
Before knotc --force conf-import knotd.conf i stopped the knotd. My knot.conf:
Btw, the interface item in the queryacl configuration is intended to be an IP address. But I guess you don't want to configure this option - it's another use case.
@fmatthiess you are right. It's a problem in the configuration import (running server with the config file is not affected). I'm going to investigate it...