Ubuntu
resolvconf package

  1. Bug #1035098
  2. Comment #2

Comment 2 for bug 1035098

Revision history for this message
Steve Langasek (vorlon) wrote : Re: TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS envvar ignored in /etc/default/resolvconf

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.