See below for the results of various commands. Prefix xx.xx is the Ethernet network while yy.yy is the wireless network. Both of them are in the public IP range (in case it matters). I also added the result of the dig command, without and with specifying a DNS server. Notice that directly querying the xx.xx server works, while querying dnsmask or an yy.yy server fails in the same way. I haven't put the tests in this message, but as you can guess, if I unplug eth0, both dnsmask and yy.yy server succeeds, and if I kill wlan0, both dnsmask and xx.xx server succeeds.
$ ip route default via xx.xx.212.190 dev eth0 proto static yy.yy.72.0/24 dev wlan0 proto kernel scope link src yy.yy.72.155 metric 2 169.254.0.0/16 dev eth0 scope link metric 1000 xx.xx.212.128/25 dev eth0 proto kernel scope link src xx.xx.212.250 metric 1 $ cat /var/run/nm-dns-dnsmasq.conf server=xx.xx.213.253 server=yy.yy.34.35 server=yy.yy.36.37 $ dig www.google.fr ... ;; AUTHORITY SECTION: fr. 8222 IN NS d.nic.fr. ... ;; Query time: 1 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) $ dig www.google.fr @xx.xx.213.253 ... ;; ANSWER SECTION: www.google.fr. 83423 IN CNAME www-cctld.l.google.com. www-cctld.l.google.com. 114 IN A 173.194.34.24 ... ;; AUTHORITY SECTION: google.com. 169795 IN NS ns2.google.com. ... ;; Query time: 1 msec ;; SERVER: xx.xx.213.253#53(xx.xx.213.253) $ dig www.google.fr @yy.yy.34.35 ... ;; AUTHORITY SECTION: fr. 2134 IN NS e.ext.nic.fr. ... ;; Query time: 1 msec ;; SERVER: yy.yy.34.35#53(yy.yy.34.35) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979067 Title: Please reenable dnsmasq --strict-order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/979067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
