*Ubuntu 16.04*
The workaround by deleting /run/resolvconf/interface/NetworkManager did not
work for me.
Removing dns=dnsmasq from /etc/NetworkManager/NetworkManager.conf did work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
This problem is present in Ubuntu 16.04 Xenial Desktop build, as well
Quick workaround:
$ rm /run/resolvconf/interface/NetworkManager
Deleting /run/resolvconf/interface/NetworkManager and re-running
ifdown/ifup will result in the /etc/network/interfaces dns-nameservers
to be populated into
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
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1384394
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
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1384394
Title:
/etc/network/interfaces:
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
In the attachment you will find the file /etc/network/interfaces and
the directory /run/resolvconf before (run-resolvconf-before.tgz) and
after (run-resolvconf-after.tgz) doing the sudo ifup br0 br1.
** Attachment added: interfaces-and-resolvconf.tgz
Just FYI the files I attached previously in interfaces-and-resolvconf.tgz was
done using my workaround mentioned above. For completeness I therefore attach
as well my /etc/resolvconf/interface-order file.
If you like I can as well perform the steps above without applying my
workaround.
**
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
** Package changed: xubuntu-meta (Ubuntu) = resolvconf (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1384394
Title:
/etc/network/interfaces: dns-nameservers
/etc/resolvconf/interface-order is only supposed to determine the order
in which interfaces are preferred as sources of DNS configuration, it
should certainly not cause the DNS servers for an interface to be
ignored completely. Please attach your full /etc/network/interfaces, as
well as the
12 matches
Mail list logo
