This is not a bug but a feature. When a loopback address is one of the
nameserver addresses then no further nameserver addresses are listed in
/etc/resolv.conf.
The reasons for this are as follows. First, it is not normally useful
to list any nameserver addresses after a loopback address. A (caching)
nameserver on the local machine is always available, so no fallback is
needed. Second, resolvconf has to tell libc resolver clients that
resolv.conf has changed every time it changes. If only the loopback
address is listed then resolv.conf doesn't change when other interfaces
are downed and upped --- so resolver clients don't have to be notified
or restarted.
In order to disable this feature, create a /etc/default/resolvconf file
with the following content:
TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS=no
See resolvconf(8) for more information.
Also significant for you may be the fact that since version 1.60
resolvconf includes dynamic nameserver information *before* information
from the base file. In earlier versions the order was reversed. See
Debian bug report #642222 (http://bugs.debian.org/642222) for the
discussion that led up to this change.
Material that should precede dynamic and "base" material in resolv.conf should
be placed in /etc/resolvconf/resolv.conf.d/head.
--
Thomas Hood
Debian resolvconf maintainers
** Bug watch added: Debian Bug tracker #642222
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642222
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917896
Title:
resolvconf no longer honors resolv.conf.d/base
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/917896/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
