Hello, trying to solve out this particullar scenario:
On turris router (version: Forris 100.3, TurrisOS 4.0-beta9):
- knot-resolver (caching, recoursive server), version: 3.2.1-3.4
- wireguard server, version: 0.0.20190601-1.0
Clients: laptos (widows, macos) and smartphones (iphone).
In both cases described bellow I am able to ping anything from connected wireguard client (router, DNS server and so on).
(A)
So here is the thing when you configure kresd as a forwarding DNS with option option forward_custom ā99_cloudflareā and connect wireguard client to wireguard server on turris router everything runs smootly. So basicaly you need to follow this KB arcticle which is about adding DoT servers: https://doc.turris.cz/doc/en/public/dns_knot_misc.
Again if you connect with your wireguard client to server everything is good including DNS resolving.
(B)
But look (in the link provided) for part called: Setup in Turris OS 3.9.6 through 3.10.8. Forwarding_upstream is acctually OFF and other settings are taken from custom.conf file which is clear. So I follow this advice so set forwarding_upstream to 0 and prepared some configuration in custom file. In custom configuration file is set of DNS servers where each supports DoT. The reason why I do this is to randomize selection of DNS server for clients queries. And this is the issue. So now if you connect with your client to wireguard server DNS resolution doesnāt work properly. Sometime works good and sometime not in other words if you try resolve name for instance bbc.com it resolves for first time, not for second, then after some time it resolves and so onā¦
Resolving is good ANYTIME (case A and B) for client on the LAN using the very same DNS server.
So the question is what actually has changed in version 3.11 and higher in resolver settings? What could be the problem of resolveng. Suppose that both configuration examples (in link provided) is basically the same so I can still use configuration style like in previous version of Turris resolver (apparently not fully), I am right?
Thank you for your help.