8 results for “mjankowski”
It turns out the root cause of this is systemd pulling all support for sysv back in March, and having systems silently break if they're still using it. So it's not just Ubuntu; every distro running systemd that still allowed init.d is likely to have this issue when to go to this version of systemd.
https://linuxjust4u.com/linux/systemd-260-sysv-removed-linux-upgrade-guide/
Update -- I checked back a little later and somehow that got overwritten and things stopped working again.
Now I've added
DNS=1.1.1.1 8.8.8.8
to /etc/systemd/resolved.conf. I won't be surprised if something overwrites that file back to its default values too, but for now it's working.
Update -- I seem to have gotten things mostly working again by running
sudo resolvectl dns eth0 1.1.1.1 8.8.8.8
I love how the attitude in the #ubuntu IRC channel is that this is my fault for never fixing something that wasn't broken and had worked fine for nearly a decade, and not theirs for making a major breaking change without warning.
I updated a server to Ubuntu 26.10 this morning. It had been happily running on Linode since 2017. When the install finished, I discovered that in in 26.10 they removed support for init.d, which broke DNS and god only knows what else on the server.
So be warned.
The View to a Kill
Industry experts predict 2050 will be the Year of Linux on the Desktop
Sixers GM Joel Embiid asks Philadelphia sports fans to "Trust the Process" as team seeks first league title in 67 years.