[Bug 1035098] Re: TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS envvar ignored in /etc/default/resolvconf

[Steve Langasek]

Hi Thomas,

> Of the files in /etc/resolvconf/resolv.conf.d/, only the "base" file has
> contents subject to truncation. 

Ok, but why should that be?  The issue isn't that there are contents
*in* /head that should be truncated; the issue is that the contents of
/head don't trigger truncation of entries from other sources, and they
really ought to.  Note that the *only* servers listed in /head in this
example are loopback.  The user actually did this at my suggestion,
because I assumed resolvconf's behavior would be to honor /head, then
discard other sources because a loopback resolver is present.

This seems the logically consistent behavior to me, even if it requires
adding additional parsing of /head that isn't currently happening.

** Changed in: resolvconf (Ubuntu)
       Status: Invalid => New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1035098

Title:
  TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS envvar ignored in
  /etc/default/resolvconf

Status in “resolvconf” package in Ubuntu:
  New

Bug description:
  I created a /etc/default/resolvconf file with the option:
  TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS="yes"
  in it.

  The contents of /etc/resolvconf/resolv.conf.d/head are:
  ########################################
  # 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

  # local resolver (unbound)
  nameserver ::1
  nameserver 127.0.0.1
  ########################################

  However, after rebooting, I still get my ISP's DNS servers below mine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1035098/+subscriptions