*** This bug is a duplicate of bug 1853164 ***
https://bugs.launchpad.net/bugs/1853164
** This bug has been marked a duplicate of bug 1853164
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Tags added: ddstreet
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1745463
Title:
Disabling systemd-resolved breaks dhclient resolvconf integration
Status in
** Tags added: resolved-resolvconf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1745463
Title:
Disabling systemd-resolved breaks dhclient resolvconf integration
Status
In this systemd github issue
https://github.com/systemd/systemd/issues/5755 in particular is
problematic darkstar states "the DNS servers are supposed to be exactly
equivalent". But as far as I can tell systemd doesn't have any provision
for temporarily falling back to a different nameserver if
If you google a bit around then you will find many issues with systemd-
resolved that could be a reason you want to be able to not use it. So I
have a strong opinion that Ubuntu should keep the flexibility to be able
to use alternative resolving configurations.
--
You received this bug
I've spent a lot of time discovering this issue, and now it is bugging
me every time there is an update of systemd, it wants to reinstall the
file again.
Actually this should be solved by making systemd-resolved a separate
package so it can actually be UNINSTALLED including files that disturb
> Can you help me understand the motivation underlying the requirement?
The motivation is that if the current dns server goes down, we don't
have to wait for the request to timeout and make another request to the
next server. Before resolved this was more of a problem since libc would
always try
Hello,
On Tue, Nov 26, 2019 at 04:42:44PM -, Thayne wrote:
> Maybe there is a better way to do this, but here is my situation. I need
> to be able to send DNS queries to multiple dns servers in parallel and
> use the first response I get back (so that I use the fastest/closest dns
> server).
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
> If there are scenarios where it is not appropriate to run resolved, then we
should absolutely evaluate those and determine how they should be supported
in Ubuntu.
Maybe there is a better way to do this, but here is my situation. I need
to be able to send DNS queries to multiple dns servers
kalvdans -- they don't get it. Inflexibility for inflexibility's sake is
the new goal. My proposed fix is very simple and safe, but because it
allows flexibility it's not going to be accepted.
Feel free to edit the broken script in the package to enable your setup
to work properly. I've done this
> I'm running a system without network-manager, without netplan, without
> resolvconf. Only ifupdown and dhclient. I expect /etc/resolv.conf to be
> updated by the logic in /sbin/dhclient-script where it (correctly, in my
> system) assumes it is the only source of dns servers. I have reopened
>
I agree with the change @GeekSmith suggests as well.
I'm running a system without network-manager, without netplan, without
resolvconf. Only ifupdown and dhclient. I expect /etc/resolv.conf to be
updated by the logic in /sbin/dhclient-script where it (correctly, in my
system) assumes it is the
I quite agree with @GeekSmith here. We disabled systemd-resolved on
bionic and install ifupdown instead since we install this on server that
have a static configuration and we don't want systemd-resolved to modify
anything in the resolv.conf file.
Only during the initial installation time of the
Just clarifying that we don't use the resolvconf package either, but
just a plain static /etc/resolv.conf file.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1745463
[Expired for resolvconf (Ubuntu) because there has been no activity for
60 days.]
** Changed in: resolvconf (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Tags added: id-5acd885138c94c5bb1f96431
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1745463
Title:
Disabling systemd-resolved breaks dhclient resolvconf integration
To distill this down to its most basic form, let's try this.
When resolvconf or resolved is installed but disabled, its DHCP hook
script still executes and potentially interferes with the proper
operation of other hook scripts.
My patch ensures that these hook scripts only run when the
What I'm trying to achieve is this: use resolvconf instead of resolved
in Ubuntu 17.10. There is a bug when one tries to do so.
This is a fresh install on a laptop using the desktop installation DVD.
resolv.conf points to /run/resolvconf/resolv.conf and is managed by
resolvconf.
I have
May I backtrack a bit, and ask how is this system configured? And is it
a desktop or a server configuration? Is it a fresh install or an
upgrade?
Specifically, what I am confused about is how the networking is
configured and where /etc/resolv.conf is pointing at.
I see that NetworkManager and
> Flexibility for flexibility's sake is not a goal of Ubuntu.
H...flexibility for the sake of making a system work seems like a
good goal. As a user of Linux for 18 years, and one that has used Ubuntu
since its very first release, I can say with confidence that Linux is
absolutely about
On Thu, Jan 25, 2018 at 11:02:35PM -, GeekSmith wrote:
> Is the use of resolvconf and ifupdown without resolved an unsupported
> configuration in 17.10?
resolvconf is in universe as of 17.10. In effect, yes, this is
unsupported.
> Is resolved the only supported DNS configuration management
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
Nothing in your bug report explains why you have taken the initial step
to disable systemd-resolved on your system. If it is simply that it is
"unwanted", that is insufficient justification for us to support a
configuration that involves disabling a component that the Ubuntu
development team has
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
25 matches
Mail list logo
