Hello,
could you please help me with knot resolver configuration in the case when I
need to redirect each variation for the domain to some address.
e.g.
www.example.com, m.example.com, domain.example.com ...
like wildcard record
*.example.com 10.0.0.50
In my configuration is it handeled by file with static records
-- load static records
hints.add_hosts('/etc/knot-resolver/static_records.txt')
which contains address to be redirected and the domain.
10.0.0.50 1xbet.com
10.0.0.50 thelotter.com
10.0.0.50 webmoneycasino.com
10.0.0.50 betworld.com
10.0.0.50 bosscasino.eu
10.0.0.50 sportingbull.com
But I´m not able to handle the correct syntax for a wildcard domain
redirection.
Best regards,
--
Smil Milan Jeskyňka Kazatel
Hi,
I am writing looking for some help with a setup where the local lan has
a machine with knot resolver and some of the hosts that are connected to
the LAN are ubuntu machines that by default use systemd-resolved as a
local caching stub resolver. For some reasons this combination appears
troublesome and I am trying to undestand all the reasons why.
One issue has already been identified as a systemd-resolved, in the
ubuntu focal version getting confused by a (correct) answer from kresd
(discussion on
https://gitlab.nic.cz/knot/knot-resolver/-/issues/686#note_234431).
Now, I find another issue in that I do not appear successful in making
systemd-resolved talk to kresd over tls. This would be important
because most of the ubuntu focal hosts are setup with systemd-resolved
using opportunistic tls. If systemd-thinks that there is a problem with
contacting the current DNS server via tls then it switches to the
fallback server and kresd ends up not being used at all.
If I use `resolvectl` to set the DNS of an ubuntu host to point to the
machine with kresd and I activate DNSoverTLS, then I get:
resolvectl query lwn.netlwn.net: resolve call failed: All attempts to contact name servers or
networks failed
Similarly, if I user resolvectl to set to use opportunistic DNSoverTLS,
things seem to work, but I see on the journal some messages about
Using degraded feature set UDP for DNS server
Thus, I'd be glad to get some pointer at how to check that DNS over TLS
works correctly with kresd and how to verify why systemd-resolved fails.
Thanks!
Sergio
Hi,
I am writing looking for some help with a setup where the local lan has
a machine with knot resolver and some of the hosts that are connected to
the LAN are ubuntu machines that by default use systemd-resolved as a
local caching stub resolver. For some reasons this combination appears
troublesome and I am trying to undestand all the reasons why.
One issue has already been identified as a systemd-resolved, in the
ubuntu focal version getting confused by a (correct) answer from kresd
(discussion on
https://gitlab.nic.cz/knot/knot-resolver/-/issues/686#note_234431).
Now, I find another issue in that I do not appear successful in making
systemd-resolved talk to kresd over tls. This would be important
because some of the ubuntu focal hosts are setup with systemd-resolved
using tls.
If I use `resolvectl` to set the DNS of an ubuntu host to point to the
machine with kresd and I activate DNSoverTLS, then I get:
resolvectl query lwn.netlwn.net: resolve call failed: All attempts to contact name servers or
networks failed
Similarly, if I user resolvectl to set to use opportunistic DNSoverTLS,
things seem to work, but I see on the journal some messages about
Using degraded feature set UDP for DNS server
Thus, I'd be glad to get some pointer at how to check that DNS over TLS
works correctly with kresd and how to verify why systemd-resolved fails.
Thanks!
Sergio