KaiXin on Nostr: I might as well be the first few to be affected the recently dropped ...
I might as well be the first few to be affected the recently dropped systemd-resolved.service in #Debian. I daily use #Debian sid and as a part of today's update, systemd-resolved.service was removed. I had to systemctl restart systemd-resolved.service every time I use VPN to connect to workplace network, which stopped working after the removal, reporting DNS resolution failure. I had to remove the softlinked /etc/resolv.conf to /run/systemd/resolve/resolv.conf and manually add some entries according to the content of /run/systemd/resolve/resolv.conf and restart network services. Thank god /run/systemd/resolve/resolv.conf was still there. #FOSS #systemd
Published at
2025-03-30 03:31:08Event JSON
{
"id": "45071d606e5dbbd89397ddf5d098d268f2ffa5d8996b441b168a161db9743755",
"pubkey": "032df67da67eebbd99f8c8530c5e071a20e9ac461c4bd5b82b009608dd7dc628",
"created_at": 1743305468,
"kind": 1,
"tags": [
[
"t",
"debian"
],
[
"t",
"debian"
],
[
"t",
"foss"
],
[
"t",
"systemd"
],
[
"proxy",
"https://snac.bsd.cafe/kaixin/p/1743305468.239503",
"activitypub"
]
],
"content": "I might as well be the first few to be affected the recently dropped systemd-resolved.service in #Debian. I daily use #Debian sid and as a part of today's update, systemd-resolved.service was removed. I had to systemctl restart systemd-resolved.service every time I use VPN to connect to workplace network, which stopped working after the removal, reporting DNS resolution failure. I had to remove the softlinked /etc/resolv.conf to /run/systemd/resolve/resolv.conf and manually add some entries according to the content of /run/systemd/resolve/resolv.conf and restart network services. Thank god /run/systemd/resolve/resolv.conf was still there. #FOSS #systemd\n",
"sig": "7bf076dcd85ab8d0695b64ae42ecc543b0fcd1513d7c647b409139cc0b193e0aee7b4acdc5ab3d0ae42b4e1b251c9c3262439bb9596ca48a8665aeb10ebb3e1a"
}