Comment 21 for bug 1671606

@Mercury

Hi, please note that the change I've made is *only* against the resolvconf task; as you say and document the issue (and potential fix) is against dnsmasq; ergo there is no need for a resolvconf patch/change.

You mention:

"and resolvconf was not properly tracking how interfaces were added and removed from the system."

I see no details or data in this bug, nor the RH bugzilla that indicates that resolvconf itself has an issue. If you have
more information on this, then please do add that;

Specifically to the recent upgrade to resolvconf (I included the diff of change); there is no runtime code change; only a systemd unit change on when the service is started. Even if there is some bug in resolvconf as you say; it will occur in the previous version and the updated version since the update did not modify any of the resolvconf runtime code.

If you believe that the *unit* change to resolvconf in 1.78ubuntu4 is related to this issue, please add that specific information before reopening the resolvconf task.

Finally, it does appear that there should be a dnsmasq task; I'll nominate that.