Thank you for the clarification with regard to the differences between the
'dnsmasq' and 'dnsmasq-base' packages.
The pointer to the resolvconf documentation, however, is less on-point,
since my previous report makes reference already to the resolvconf
documentation. Clearly, this isn't a ques
> Is dnsmasq getting its DNS server information from resolvconf,
> which in turn gets it from /etc/network/interfaces? Or, does
> dnsmasq take what it likes from /etc/network/interfaces directly,
> discarding the rest?
1. If you have only the dnsmasq-base and network-manager packages installed
t
I mean of course that resolvconf documentation refers to using dns-
nameservers (not "dns-server" as I wrote above).
I've added this as affecting dnsmasq-base, too. I think this is, at
least, a documentation bug with regard to the interplay amongst
resolvconf and dnsmasq and their configuration f
The use of TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS=no is defined
in the resolvconf documentation.
However, the resolvconf documentation also says that one should be able
to use dns-server settings in /etc/network/interfaces
This inconsistency is frustrating: Is dnsmasq getting its DNS se
On Tue, Feb 25, 2014 at 16:10:50 -, Stéphane Graber wrote:
> By default, resolvconf will truncate the list of DNS servers after the
> loopback address. This can be overriden by putting
> TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS=no in
> /etc/default/resolvconf
>
> This behaviour is docum
By default, resolvconf will truncate the list of DNS servers after the
loopback address. This can be overriden by putting
TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS=no in
/etc/default/resolvconf
This behaviour is documented in resolvconf's manpage.
** Changed in: resolvconf (Ubuntu)
S
