DNS Domain: ~mydomain.com means that said domain got added as "route_only" to systemd-resolved.
We need to find who/what/why did this.
This could be the configuration of resolved.conf, networkd, or network-manager itself.
Can we make sure there is nothing suspicious in:
$ grep Domains= /etc/systemd/resolved.conf \ /etc/systemd/resolved.conf.d/* \ /run/systemd/resolved.conf \ /run/systemd/resolved.conf.d/* \ /lib/systemd/resolved.conf \ /lib/systemd/resolved.conf.d/* \ /usr/lib/systemd/resolved.conf \ /usr/lib/systemd/resolved.conf.d/* \ /etc/systemd/network/* \ /etc/systemd/network/*.d/* \ /run/systemd/network/* \ /run/systemd/network/*.d/* \ /lib/systemd/network/* \ /lib/systemd/network/*.d/* \ /usr/lib/systemd/network/* \ /usr/lib/systemd/network/*.d/*
I expect loads of errors, and just '/etc/systemd/resolved.conf:#Domains=' to turn up.
That should exclude any systemd-resolved / networkd configurations.
And I'll start digging into network-manager resolved-dns plugin code.
DNS Domain: ~mydomain.com means that said domain got added as "route_only" to systemd-resolved.
We need to find who/what/why did this.
This could be the configuration of resolved.conf, networkd, or network-manager itself.
Can we make sure there is nothing suspicious in:
$ grep Domains= /etc/systemd/ resolved. conf \ resolved. conf.d/ * \ resolved. conf \ resolved. conf.d/ * \ resolved. conf \ resolved. conf.d/ * \ systemd/ resolved. conf \ systemd/ resolved. conf.d/ * \ network/ * \ network/ *.d/* \ network/ * \ network/ *.d/* \ network/ * \ network/ *.d/* \ systemd/ network/ * \ systemd/ network/ *.d/*
/etc/systemd/
/run/systemd/
/run/systemd/
/lib/systemd/
/lib/systemd/
/usr/lib/
/usr/lib/
/etc/systemd/
/etc/systemd/
/run/systemd/
/run/systemd/
/lib/systemd/
/lib/systemd/
/usr/lib/
/usr/lib/
I expect loads of errors, and just resolved. conf:#Domains= '
'/etc/systemd/
to turn up.
That should exclude any systemd-resolved / networkd configurations.
And I'll start digging into network-manager resolved-dns plugin code.