@jz Sounds like a Debian or apt issue… systemd-resolved works fine on my Fedora machines… Systemd rocks!

@jz It would have been much more productive to find out what was broken before killing everything, and if by asking for help. But this way your rumbling makes no much sense.

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.

@jz after full-upgrade . The usual /etc/apt/sources.list and *.list files in /etc/apt/sources.list.d/ are replaced by new files, located in the same directory, but with the .sources extension and using the more readable and structured deb822 format. convert all your existing files to this format, you can run:
''apt modernize-sources''

Sources: Linuxiac & lecrabeinfo

@ploum oui cela ressemble à ça... mais ça marchait avant le passage à Trixie... je vais faire le menage dans /etc/network...

pffff ces jeunes avec leur systemd, j'te jure....

#vieux

@bonifartius current lead: https://news.ycombinator.com/item?id=43509615

(unsure now, as resolvconf returns my dns servers for my interface!)

@bonifartius maybe...? i removed any "connection" in the network-manager graphical interface, and configured manually /etc/systemd/network/lan.network to my parameters, including DNS server, etc..

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...