Ubuntu
resolvconf package

Improve resolved integration

Bug #1889068 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
New
Undecided
Unassigned
isc-dhcp (Ubuntu)
Fix Released
Undecided
Unassigned
resolvconf (Ubuntu)
New
Undecided
Unassigned
systemd (Ubuntu)
New
Undecided
Unassigned

Bug Description

Insure that ifupdown & dhcp DNS information is always added to resolved.

Move the resolved hooks from systemd package to isc-dhcp-client and ifupdown themselves.

Figure out how to integrate "eth0" resolver => Manager resolver.

Blog / document how to control this.

See original description
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Preparing uploads in https://bileto.ubuntu.com/#/ticket/4162

description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package isc-dhcp - 4.4.1-2.1ubuntu9

---------------
isc-dhcp (4.4.1-2.1ubuntu9) groovy; urgency=medium

  * Revert 4.4.1-2.1ubuntu8, network-manager autopkgtests regress on
    ppc64el.

 -- Dimitri John Ledkov <email address hidden> Wed, 12 Aug 2020 10:33:55 +0100

Changed in isc-dhcp (Ubuntu):
status: New → Fix Released
Dan Streetman (ddstreet)
tags: added: resolved-resolvconf
Revision history for this message
Lukas Märdian (slyon) wrote :

We need to make sure that the resolved hooks use the correct "systemd-resolve" user to setup the statedir permissions inside the hook, see LP: #1896772

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.