Maybe interesting: systemd-resolve --status eth2 always reports the correct, internal DNS server, even though names are incorrectly resolved to their public IPs (I tried resolving with both dig and systemd-resolve).
gpothier@tadzim3:~$ systemd-resolve --status eth2
Link 3 (eth2)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.0.2
DNS Domain: ozone.caligrafix.cl
Also, sudo systemd-resolve --flush-caches temporarily solves the problem, in the same way restarting the service does.
Maybe interesting: systemd-resolve --status eth2 always reports the correct, internal DNS server, even though names are incorrectly resolved to their public IPs (I tried resolving with both dig and systemd-resolve).
gpothier@tadzim3:~$ systemd-resolve --status eth2
Link 3 (eth2)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.0.2
DNS Domain: ozone.caligrafix.cl
Also, sudo systemd-resolve --flush-caches temporarily solves the problem, in the same way restarting the service does.