Conversation

Notices

1. Embed this notice
   KaiXin (kaixin@snac.bsd.cafe)'s status on Thursday, 10-Apr-2025 04:21:37 JST KaiXin
   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
   
   • Embed this notice
     daltux (daltux@snac.daltux.net)'s status on Thursday, 10-Apr-2025 04:21:26 JST daltux

     in reply to
     I believe you could let #NetworkManager set /etc/resolv.conf with data it receives from DHCP for each connection. Removing the symlink, or pointing it to /run/NetworkManager/no-stub-resolv.conf, and then systemctl restart NetworkManager.service would do it. Maybe you also have to change /etc/NetworkManager/NetworkManager.conf before that. For details, see NetworkManager.conf manual page on options dns and rc-manager.
     
     #Debian #systemd
     
   • Embed this notice
     daltux (daltux@snac.daltux.net)'s status on Thursday, 10-Apr-2025 07:08:19 JST daltux

     in reply to
     @kaixin@snac.bsd.cafe Please let me know if/how you definitively resolved it 😅
     
   • Embed this notice
     KaiXin (kaixin@snac.bsd.cafe)'s status on Thursday, 10-Apr-2025 07:08:21 JST KaiXin

     in reply to

     • daltux
     Thanks for the detailed instructions my friend