Turns out that resolvconf always filters out comments, so the only way
to get a comment in there is via /etc/resolvconf/resolv.conf.d/head. So
moving package.
** Package changed: systemd (Ubuntu) => resolvconf (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touc
If such a comment were to be added then in order not to mislead it would
have to take into account the configurability of various components. So
you'd have to say something like:
«If the line "nameserver 127.0.0.53" is present then it probably refers
to the systemd resolver listening on the loopba
Right, the comment would need to be conditional. My original naïve
approach was to add the comment together with the nameserver, such as
printf "# Run systemd-resolve --status blabla\nnameserver 127.0.0.53\n"
| /sbin/resolvconf -a systemd-resolved
so that the comment would only be there when appr
Right, I think the file should only document the Ubuntu-specific things
such as the facts that by default resolvconf and the systemd resolver
are used, NetworkManager is used by default on Desktop and ifup on
Server, and so on. There have been hundreds of questions about these
basic things on AskUb
** Changed in: resolvconf (Ubuntu)
Assignee: Martin Pitt (pitti) => Canonical Foundations Team
(canonical-foundations)
** Changed in: resolvconf (Ubuntu)
Milestone: ubuntu-16.11 => ubuntu-16.12
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
** Changed in: resolvconf (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) => Steve
Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/
I have a fix for resolvconf here, but it's inaccurate for the desktop
because Network Manager is still doing dnsmasq by default. Opening a
task for NM.
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Status: New
** Changed in: network-manager (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) => Steve
Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad
https://blueprints.launchpad.net/ubuntu/+spec/foundations-y-local-
resolver has the two outstanding issues to switch NM over to resolved
too. These are unblocked now: the new resolved DNS plugin is in upstream
master since around September, and NM 1.4 landed in zesty-proposed
yesterday. Let's land
This bug was fixed in the package resolvconf - 1.79ubuntu2
---
resolvconf (1.79ubuntu2) zesty; urgency=medium
* etc/resolvconf/resolv.conf.d/head: add comment about
'systemd-resolve --status', since systemd-resolved is now in use in all
but the most unusual configurations, a
This bug was fixed in the package network-manager - 1.4.2-2ubuntu4
---
network-manager (1.4.2-2ubuntu4) zesty; urgency=medium
[ Martin Pitt ]
* Add resolved DNS plugin (backported from upstream master).
* Disable resolvconf support.
This is broken with DNS plugins other than
Martin,
Please note, that in my setup, the network is lost immediately after
rebooting with the new network-manager (1.4.2-2ubuntu4). Then,
downgrading back to version 1.4.2.-2ubuntu3, and rebooting, I get
network back.
In both of these versions, the network-manager creates the same kind of
file
On Fri, Nov 04, 2016 at 11:53:11AM -, Thomas Hood wrote:
> What would be far better, though, is to include a text file or manpage
> explaining how name service currently works in Ubuntu.
That doesn't help the problem that /etc/resolv.conf is the file that the
experienced admin expects to conta
Hello Harry,
Harry [2016-12-03 15:02 -]:
> Please note, that in my setup, the network is lost immediately after
> rebooting with the new network-manager (1.4.2-2ubuntu4).
Thanks for filing bug 1647133, tracking that issue there.
--
You received this bug notification because you are a member
14 matches
Mail list logo
