[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
Bugs, which is subscribed to Ubuntu.
** Changed in: resolvconf (Ubuntu)
Status: Expired => New
** Changed in: resolvconf (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473727
Title:
No
[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
Bugs, which is subscribed to Ubuntu.
Is the resolvconf package even installed?
Assuming it is, why doesn't it get called when the interfaces are
configured?
Can things be changed so that resolvconf does get called in the normal
way when interfaces are configured? (The normal way and all other
things resolvconf are explained in
Yes, resolvconf is installed, and calls the supplied script - which I
now notice needs the banner comment correcting - I'll provide an updated
script as an attachment.
The key to understanding this issue is that it's a diskless machine
booting via DHCP and using NFS to provide a root partition
Here is a rough draft, untested, of a script that would be run once in
the main boot sequence in order to bring the resolvconf database up to
date. The main difference from your script is that it sends the info to
resolvconf instead of writing directly to resolv.conf. (I am assuming
that
The VM image was generated via debootstrap, then the main changes were:
- add interfaces definitions for lo (auto) and eth0 (manual)
- set hostname
- set root password
- set fstab up (mounting / from /dev/nfs)
- install linux-virtual package via chroot
- set initramfs-tools for netboot run
Hi there and thanks for your report.
I don't see any evidence here of a bug in resolvconf. There is most
probably something wrong with your machine's configuration. So this
report should be reassigned to something else... or closed if the
configuration shortcomings are purely local. Where did you
Here's a script that works for me (put in /etc/resolvconf/update.d
please include in the package.
#!/bin/sh
#
# Script to update every forwarding djbdns dnscache instance running
# on the local machine
#
# this script sets up every FORWARDONLY dnscache managed by either
# daemontools or runit
