Systemd Resolved Fallback DNS causes problems resolving internal subdomains.

[Digital-Storm]

Is it possible to have a feature or change in behavior for Systemd Resolved to use the same DHCP DNS servers for Fallback DNS, that way the system isn't trying to bypass DNS received from DHCP by default? In my example, internal DNS records are being overridden by public records, this is an issue for things like Pihole, Technetium, Conditional Forwarding for subdomains, etc. The default fallback resolvers bypass internal DNS and overwrite the cache of Resolved causing subsequent DNS queries to fail.

Maybe a toggle to "set Fallback DNS to DHCP/Static"

Example of current output
resolvectl status
Global
Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign
Current DNS Server: 192.168.20.111
DNS Servers: 9.9.9.9#dns.quad9.net 2620:fe::9#dns.quad9.net 1.1.1.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 8.8.8.8#dns.google 2001:4860:4860::8888#dns.google

    DNS Domain: ~.

Link 2 (eno1)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6
Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
DNS Servers: 192.168.1.1
DNS Domain: mydomain.com
Default Route: yes

This is accomplished through /etc/systemd/resolved.conf.d/dns.conf
[Resolve]
DNS=192.168.1.1
FallbackDNS=