Thanks! Obviously, I should have read a little further in the manpage.
My error... Do I need to do anything to close out or dismiss that bug report? Regards, Dave Knight Radford, VA On Wed, Feb 17, 2016 at 11:28 AM, Thomas Hood <1546...@bugs.launchpad.net> wrote: > The content of the base file is processed, but due to resolvconf's rules > they may fail to show up in resolv.conf. Comments in the base file get > discarded. Lines like "nameserver w.x.y.z" are omitted if another line > is, e.g., "nameserver 127.0.1.1.". If you set > TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS=n in > /etc/default/resolvconf then "nameserver" lines from the base file will > be included. > > ** Changed in: resolvconf (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1546624 > > Title: > resolvconf -u does not incorporate /etc/resolvconf/resolv.conf.d/base > file into /etc/resolv.conf > > Status in resolvconf package in Ubuntu: > Incomplete > > Bug description: > > ============================== Requested Info > ====================================================== > > System details > > This may be a generic problem with Debian resolvconf, as it has been a > long-standing issue in my lab, since I run a local DNS server, and I > have reproduced it on several hosts running Debian derivatives: > > Ubunti 14.04.3 LTS systems, e.g: > $ uname -a > Linux leno 3.19.0-49-generic #55~14.04.1-Ubuntu SMP Fri Jan 22 > 11:23:34 UTC 2016 i686 i686 i686 GNU/Linux > > $ apt-cache policy resolvconf > resolvconf: > Installed: 1.69ubuntu1.1 > Candidate: 1.69ubuntu1.1 > Version table: > *** 1.69ubuntu1.1 0 > 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main > i386 Packages > 100 /var/lib/dpkg/status > 1.69ubuntu1 0 > 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 > Packages > > Mint: > $ uname -a > Linux nas2 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC > 2014 x86_64 x86_64 x86_64 GNU/Linux > > $ apt-cache policy resolvconf > resolvconf: > Installed: 1.69ubuntu1.1 > Candidate: 1.69ubuntu1.1 > Version table: > *** 1.69ubuntu1.1 0 > 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main > i386 Packages > 100 /var/lib/dpkg/status > 1.69ubuntu1 0 > 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 > Packages > > raspbian: > $ uname -a > Linux raspi2 4.1.17-v7+ #834 SMP Mon Feb 1 15:17:54 GMT 2016 armv7l > GNU/Linux > > $ apt-cache policy resolvconf > resolvconf: > Installed: 1.67 > Candidate: 1.67 > Version table: > *** 1.67 0 > 500 http://mirrordirector.raspbian.org/raspbian/ wheezy/main > armhf Packages > 100 /var/lib/dpkg/status > > ------------------------------------------------------------------ > > What I expected to happen: > > The man page for resolvconf states: > > The dynamically generated resolver configuration file always > starts > with the contents of /etc/resolvconf/resolv.conf.d/head and > ends with > the contents of /etc/resolvconf/resolv.conf.d/tail. Between > head and > tail the libc script inserts dynamic nameserver information > compiled > from, first, information provided for configured interfaces; > second, > static information from /etc/resolvconf/resolv.conf.d/base. > > What happens instead: > > Updating /etc/resolv.conf (which is a symlink to > /run/resolvconf/resolv.conf) with resolvconf -u dappears to do > everything EXCEPT incorporate the contents of the > /etc/resolvconf/resolv.conf.d/base file. > > ============== My analysis and steps to reproduce the problem > ======================================== > > The resolvconf manpage and many web resources claim that one can make > "permanent changes" (e.g. local nameserver, search domain, etc) by > editing the /etc/resolvconf/resolv.conf.d/base file, and that > executing "resolvconf -u" build a new /etc/resolv.conf (actually > /run/resolvconf/resolv.conf) from the contents of the head, base and > tail files in /etc/resolvcond/resolv.conf.d. > > In fact, resolvconf -u does incorporate the head and tail files, but > not the base file. > > Steps to reproduce: > > 1 - on a system that has resolvconf installed, display the content of > /etc/resolv.conf, e.g.: > > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > nameserver 127.0.1.1 > > 2 - cd /etc/resolvconf/resolv.conf.d > > 3 - (as root) edit the head, base and tail files, by adding an > identifying comment line, e.g.: > > # this is the head file > > # this is the base file > > # this is the tail file > > 4 - (as root) run resolvconf -u > > 5 - Again, display the content of /etc/resolv.conf: > > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > # this is the head file > nameserver 127.0.1.1 > # this is the tail file > > Note that the content of the head and tail files has been > incorporated, but the content of the base file has not.. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1546624/+subscriptions > -- The "Safe in Church" deception: believing that calling some building a "sanctuary" will magically deter criminal violence is a dangerous delusion! The "Gun-Free Zone" deception: believing that a "No Guns" policy or sign will deter criminal violence is "magical thinking" in its most dangerous form! In your time of need, may your piece be with you! ** Changed in: resolvconf (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546624 Title: resolvconf -u does not incorporate /etc/resolvconf/resolv.conf.d/base file into /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1546624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
