Hi Farkas,
I think you need more traditional dns cache like dnsmasq or unbound. I
don't think there is a good syntax to configure per-domain nameservers,
which would be implementation independent. I think the way to go would
be to make forwarding declarations on VPN provided nameservers. It
On Thu, Apr 27, 2023 at 02:46:09PM +0200, Farkas Levente wrote:
> What I'd like to achieve:
> - if the vpn is not connected
> - all dns query goes to 8.8.8.8
> - if vpn is connected:
> - netbird.cloud goes to 100.76.1.2
> - a.com goes through wt0 to 1.2.3.4
> - b.com goes through wt0 to
On 2023. 04. 29. 12:18, Reto wrote:
On Thu, Apr 27, 2023 at 02:46:09PM +0200, Farkas Levente wrote:
What I'd like to achieve:
- if the vpn is not connected
- all dns query goes to 8.8.8.8
- if vpn is connected:
- netbird.cloud goes to 100.76.1.2
- a.com goes through wt0 to 1.2.3.4
-
Hi,
I already read many docs about systemd-resolved, but still to able to
solve my very simple use case for name resolution.
Suppose we've two (not only one!) private/internal domain and both of
them have a separate dns server. eg:
- domain: a.com dns: 1.2.3.4
- domain: b.com dns: 5.6.7.8
