26 Čen
2020
26 Čen
'20
19:27
Hello all,
I am trying to configure my local PC (always on server), to serve DNS
resolving all other computers in my LAN. I installed and enabled the
service. I've attempted configuration. Knot-resolver correctly resolves
DNS querier on localhost machine, but fails to reply to queries from
other LAN machines.
Can someone please share configuration which I should use to have LAN
resolving?
I've tried various net.listen(), net() in config file, to no avail. I've
studied this page
https://knot-resolver.readthedocs.io/en/stable/daemon-bindings-net_server.h…
but I have no idea which option I should put in config to enable my
server PC (192.168.1.44) to allow all PCs in LAN (192.168.1.xxx) to use
knot-resolver.
I'd appreciate if someone with knowledge would help a newbie like me.
Thank you!
pioruns
26 Čen
26 Čen
22:12
On 26/06/2020 18:27, pioruns2019(a)gmx.com wrote:
Hello all,
I am trying to configure my local PC (always on server), to serve DNS
resolving all other computers in my LAN.
New info:
My systemd says following:
# systemctl status kresd(a)1.service
● kresd(a)1.service - Knot Resolver daemon
Loaded: loaded (/lib/systemd/system/kresd@.service; disabled;
vendor preset: enabled)
Active: active (running) since Fri 2020-06-26 18:36:16 BST; 37min ago
TriggeredBy: ● kresd-tls.socket
● kresd-control(a)1.socket
● kresd.socket
Docs: man:kresd.systemd(7)
man:kresd(8)
Main PID: 107295 (kresd)
Tasks: 1 (limit: 38412)
Memory: 5.3M
CGroup: /system.slice/system-kresd.slice/kresd(a)1.service
└─107295 /usr/sbin/kresd --config=/etc/knot-resolver/kresd.conf
Jun 26 18:36:16 debian-ryzen systemd[1]: Starting Knot Resolver daemon...
Jun 26 18:36:16 debian-ryzen kresd[107295]: [system] bind to
'192.168.1.47@53' Permission denied
Jun 26 18:36:16 debian-ryzen systemd[1]: Started Knot Resolver daemon.
Why would root service have Permission denied to listen a port? :(
I am using Debian Buster AMD64.
23:12
On 26/06/2020 19:27, pioruns2019(a)gmx.com wrote:
Hi pioruns,
You need net.listen('192.168.1.44') to make Knot listen on the LAN
interface. It will then receive queries and answer them. You should not
need any more configuration.
Regards,
Anand
I am trying to configure my local PC (always on
server), to serve DNS
resolving all other computers in my LAN. I installed and enabled the
service. I've attempted configuration. Knot-resolver correctly resolves
DNS querier on localhost machine, but fails to reply to queries from
other LAN machines.
Can someone please share configuration which I should use to have LAN
resolving?
I've tried various net.listen(), net() in config file, to no avail. I've
studied this page
https://knot-resolver.readthedocs.io/en/stable/daemon-bindings-net_server.h…
but I have no idea which option I should put in config to enable my
server PC (192.168.1.44) to allow all PCs in LAN (192.168.1.xxx) to use
knot-resolver.
I'd appreciate if someone with knowledge would help a newbie like me.
Thank you!
pioruns
27 Čen
27 Čen
14:56
Hello Anand,
Thanks for your reply!
On 26/06/2020 22:12, Anand Buddhdev wrote:
On 26/06/2020 19:27, pioruns2019(a)gmx.com wrote:
Hi pioruns,
You need net.listen('192.168.1.44') to make Knot listen on the LAN
interface. It will then receive queries and answer them. You should not
need any more configuration.
Actually, I finally found correct information and fixed it. Info I was
looking for was in kresd.systemd(7) manual. I just wish it would be in
online manual https://knot-resolver.readthedocs.io/ which I approached
first, but there was nothing there, and on systemd OSes putting network
declaration doesn't work because it doesn't have privileges to listen to
a port.
So, accordining to manual, in systemd OSes, *nothing* needs to be
written in kresd.conf (regarding network). Instead, I put:
[Socket]
ListenStream=192.168.1.44:53
ListenDatagram=192.168.1.44:53
via systemctl edit kresd.socket. And it works :)
29 Čen
29 Čen
8:03
Hello.
On 6/27/20 2:56 PM, pioruns2019(a)gmx.com wrote:
Actually, I finally found correct information and
fixed it. Info I was
looking for was in kresd.systemd(7) manual. I just wish it would be in
online manual https://knot-resolver.readthedocs.io/ which I approached
first
I believe your problem was primarily in kresd version mismatch. You
appear to be using older version, presumably 3.2.1-* but that one is old
and now the configuration of this is different. You can choose the
version in https://knot-resolver.readthedocs.io but I understand that
it's easy to miss significance of that.
In any case, people most likely want to avoid these old versions, as we
don't support them and for instance 3.2.1 contains multiple security
bugs (that have been published for a long time). Debian unstable
currently contains a fresh version but generally you might prefer our
own repositories; see https://www.knot-resolver.cz/download/
--Vladimir
14:14
On 29/06/2020 07:03, Vladimír Čunát wrote:
I believe your problem was primarily in kresd version
mismatch. You
appear to be using older version, presumably 3.2.1-* but that one is old
and now the configuration of this is different. You can choose the
version in https://knot-resolver.readthedocs.io but I understand that
it's easy to miss significance of that.
In any case, people most likely want to avoid these old versions, as we
don't support them and for instance 3.2.1 contains multiple security
bugs (that have been published for a long time). Debian unstable
currently contains a fresh version but generally you might prefer our
own repositories; see https://www.knot-resolver.cz/download/
Hello Vladimír,
Thank you. My problem is solved now completely.
Debian Stable is indeed using old, insecure version, with latest NXNS
problem unresolved. I hope they will push new knot-resolver version to
main repo. In the meantime, I installed package you mentioned, I got now
sources.list entry and repository key installed nicely. Package is
upgraded. I modified config file accordingly to new docs, and old socket
files for systemd are not longer needed.
Thanks!
Kind regards,
pioruns
1405
days inactive
1408
days old
knot-resolver-users@lists.nic.cz
5 comments
3 participants
participants (3)
-
Anand Buddhdev -
pioruns2019＠gmx.com -
Vladimír Čunát