On my side, I just want to use what is already bundled with Ubuntu,
systemd-resolved.service(8). I symlinked
/run/systemd/resolve/resolv.conf to /etc/resolv.conf but now I'm stuck
with this ubuntu-minimal dependency.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Martin-Éric wrote:
I just noticed another issue with this: until now, the /etc/resolv.conf
generated by network-manager would contain both domain and
search stanzas. Now, it only contains search.
Steve wrote:
I have noticed this as well, but I haven't been able to determine
that this makes
Speeding up DNS search did not require adding resolvconf
to ubuntu-minimal.
Instead, enabling dhclient's option to always prepend
127.0.0.1 to /etc/resolv.conf does the trick quite nicely.
If you only have one interface configurer (e.g., dhclient) then there is no
problem having that
Just read what Steve wrote in #13:
- nothing should be writing to /etc at runtime;
it's a bug that causes Ubuntu to not work out
of the box with a read-only rootfs
- even when not booting with a read-only rootfs,
there is a race condition between mounting /
rw and running dhclient, the
** Changed in: ubuntu-meta (Ubuntu)
Importance: Undecided = High
** Changed in: ubuntu-meta (Ubuntu)
Assignee: (unassigned) = Stéphane Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The resolvconf we promoted to main for Precise is pretty different from
the resolvconf we used to have in the past.
This has been done after discussion with the various teams as part of:
https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-dns-resolving
The corresponding MIR can be found
That work-around won't allow dhclient to update the content for as long
as resolvconf is installed, so it's not a solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922578
Title:
please remove
The MIR itself looks quite promising, but I'll emphasize that the
current implementation still breaks DNS in a chroot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922578
Title:
please remove
Oh, indeed, the dhclient hook is broken, it should only trigger if
/etc/resolv.conf is a link. I'll be uploading a fixed resolvconf
shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922578
** Package changed: ubuntu-meta (Ubuntu) = resolvconf (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922578
Title:
please remove 'resolvconf' from ubuntu-minimal Depends
To manage
Should there also be a fix to NOT update /etc/resolv.conf with a
symbolic link to /run/resolvconf/resolv.conf if we are in a chroot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922578
Title:
This bug was fixed in the package resolvconf - 1.63ubuntu5
---
resolvconf (1.63ubuntu5) precise; urgency=low
[ Stéphane Graber ]
* Instead of creating the symlink in debian/postinst, create a flag
at /var/lib/resolvconf/convert and create the symlink in the upstart
or
Additionally, resolvconf is generally known as a seriously broken
piece of software
Resolvconf was seriously broken *in Ubuntu universe* for a long time because no
one bothered to port it to upstart. In Debian the package has been in good
shape for many years.
--
Thomas Hood
--
You
This still doesn't resolve the issue. In order to function, a chroot
needs /etc/resolv.conf copied from the host's normal /etc/resolv.conf,
but because of the current implementation, the host's /etc/resolv.conf
content will always be nameserver 127.0.0.1 which is entirely useless
inside the
Last I checked, a chroot was still in the same network namespace as the
host, meaning that nameserver 127.0.0.1 reaches the dnsmasq running
outside of the chroot and will resolve just fine.
Besides the fact that /etc/resolv.conf contains 127.0.0.1 is in no way a
result of the change to
I just noticed another issue with this: until now, the /etc/resolv.conf
generated by network-manager would contain both domain and search
stanzas. Now, it only contains search.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Speeding up DNS search did not require adding resolvconf to ubuntu-
minimal. Instead, enabling dhclient's option to always prepend 127.0.0.1
to /etc/resolv.conf does the trick quite nicely. Heck, I even filed a
bug against dhclient, asking for this to be enabled by standard, a while
back.
--
You
I just noticed another issue with this: until now, the /etc/resolv.conf
generated by network-manager would contain both domain and search
stanzas. Now, it only contains search.
I have noticed this as well, but I haven't been able to determine that
this makes a difference functionally. If you
18 matches
Mail list logo
