Post AscCCfaSWe94eVraqG by kaixin@snac.bsd.cafe
 (DIR) More posts by kaixin@snac.bsd.cafe
 (DIR) Post #AscCCe4s8bHhyG4qy8 by kaixin@snac.bsd.cafe
       2025-03-30T03:31:08Z
       
       0 likes, 0 repeats
       
       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
       
 (DIR) Post #AscCCer5FLqiNmdM7E by uhuru@snac.el-hoyo.net
       2025-03-31T10:37:57Z
       
       0 likes, 0 repeats
       
       not the first : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101532 :)you might want to revert to an earlier systemd-resolved version and pin it, till #systemd #drama unfolds.. (or just use a better alternative?)
       
 (DIR) Post #AscCCfaSWe94eVraqG by kaixin@snac.bsd.cafe
       2025-03-31T13:31:22Z
       
       0 likes, 0 repeats
       
       @uhuru@snac.el-hoyo.net thanks. I am managed to get the said application work by a little tweaking with DNS. Nothing beyond that required my attention now.