Discussion
long story short i ended up making a fresh Trixie install, which took 1-2h total, after spending a good 6h trying to figure that out... with dependency hell on a systemd-resolved that was not installed in what appeared to have been a badly updated (!) system....
lessons learned: i think i dislike systemd even more now, and will stick to devuan on my main machine.... debian still r0x though.
thanks to everyone to weighed in with support and insightful suggestions!
I don’t like how some changes around systemd-resolved have been implemented. But nothing in it should break traditional use of /etc/resolv.conf, and if you had to change it by hand.
Sources: Linuxiac & lecrabeinfo
("chattr +i" helps with files changing ;)
@bonifartius current lead: https://news.ycombinator.com/item?id=43509615
(unsure now, as resolvconf returns my dns servers for my interface!)
guess the old rigged together stuff using dnsmasq was just fine :)
What is comical is i find this: https://unix.stackexchange.com/questions/442598/how-to-configure-systemd-resolved-and-systemd-networkd-to-use-local-dns-server-f
and
https://serverfault.com/questions/1008355/adding-a-new-dns-server-with-systemd-resolved
but i dont even have the systemd-resolve command, nor resolvectl .... and hard to install them as i am... offline :)
maybe i didnt upgrade correctly?
pfff...
A space for Bonfire maintainers and contributors to communicate