br matching was added to interface-order in Debian release 1.77, thus in
wily which has resolvconf 1.77ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1384394
Title:
Also: the suggested workaround didnt actually work for me. on 15.10 /
wily
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1384394
Title:
/etc/network/interfaces: "dns-nameservers"
So why isnt br* already listed by default in the file /etc/resolvconf
/interface-order ? There are many other entries for everything else. And
presumably it should do no harm / detriment.
Should that not be the fix here?
br* bridge interfaces are a common class of network devices and are
being
I gather that you want to use the fact that the resolver happens to try
one address after another, in the order that they are listed in
resolv.conf, as a way of giving precedence of one domain name system
(the service provided over the br* interfaces) over another domain name
system (the one
Ok. So the crucial thing shown here is that in addition to the br
interfaces, you have NetworkManager. NetworkManager sets 'nameserver
127.0.1.1', which by design will redirect DNS requests to a local
dnsmasq proxy, with dnsmasq itself picking up the configured nameservers
instead; and when set,
Thank you for the detailed analysis - regarding:
... since NetworkManager should still be processed and the 127.0.1.1 should
still take precedence ...
Actually for me it is important that the 127.0.1.1 does not take precedence
but instead my local name-servers take precedence (because when my
