The hasty push to replace resolvconf with resolved is having disastrous consequences. User experience and system stability should be valued over forced migration to an unproven, poorly tested, and in many cases unwanted new system.
Name resolution is one of the fundamental building blocks of a networked system. I don't understand the eagerness to change it so quickly. It almost seems careless. One might argue that all of systemd has been pushed on the user in a like manner, but I won't go there...at least it's not upstart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745463 Title: Disabling systemd-resolved breaks dhclient resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
