Comment 29 for bug 448095

Ok, I've tried with all your latest, and basically nothing has changed, it's
all still broken. On system boot, resolv.conf remains blank (or rather, it
is created, but with no entries, only the top comment lines).

ifdown/ifup fixes the problem. Same as the Ubuntu release problem.

Have you tried with vpnc or similar tunnel installed?

Does anything from /sbin/resolvconf get logged that I can read or send to
you?

+Reardon

On Sat, Dec 26, 2009 at 7:11 PM, Sander van Grieken <sander@3v8.net> wrote:

> Found one more tiny bug. fixed it and replaced /sbin/resolvconf
> attachment.
>
>
> ** Attachment added: "/sbin/resolvconf"
> http://launchpadlibrarian.net/37215643/resolvconf
>
> ** Attachment removed: "replacement for /sbin/resolvconf"
> http://launchpadlibrarian.net/37141756/sbin.resolvconf
>
> --
> resolvconf starts after ifupdown, does not pick the dns-nameserver and
> dns-search lines up from /etc/network/interfaces
> https://bugs.launchpad.net/bugs/448095
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “ifupdown” package in Ubuntu: Won't Fix
> Status in “resolvconf” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: resolvconf
>
> ifdown -a ; ifup -a fixes the problem after a reboot.
>
> ProblemType: Bug
> Architecture: i386
> Date: Sat Oct 10 17:55:06 2009
> DistroRelease: Ubuntu 9.10
> Package: resolvconf 1.44ubuntu1
> PackageArchitecture: all
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-13.43-generic
> SourcePackage: resolvconf
> Uname: Linux 2.6.31-13-generic i686
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/448095/+subscribe
>
>