Comment 3 for bug 1745463

Is the use of resolvconf and ifupdown without resolved an unsupported configuration in 17.10? Is resolved the only supported DNS configuration management system in Ubuntu 17.10? There are many users who value the control and flexibility of pre-resolved systems and do not want a local caching nameserver.

The inadequacy is that systemd breaks resolvconf. I highly doubt that resolvconf will be removed from the archives in 18.04 because resolved is clearly not ready. Look at the number of upgrade issues and bugs filed against it.

There are too many systems, mainly servers, that cannot or should not run a nameserver, not even a local one. resolved is not ready to service these systems.

Because resolved is packaged with systemd, one cannot choose to run systemd without resolvd. This coupling makes the system less flexible and more fragile. There's another inadequacy for you.

Not only have I discovered a bug, I have given the solution to the bug in two packages. My proposed solution does not affect performance nor hinder proper behavior in any way. It simplifies interface configuration. This simple fix should be favored over the removal of software that is stable, functional, and time-tested.

Denying the existence of the bug doesn't make it go away. I've reported the defect and provided a simple fix. The Ubuntu team can patch the scripts or leave them broken.