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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1035098
Title:
TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS envvar ignored in
/etc/default/resolvconf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1035098/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
