I've been reading through the lengthy discussion at bug #1003842 (dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers) which seems related. I'm about halfway so I don't know what the resolution was in the end (if any). In any case the discussion is very interesting. It explores the subject of non- equivalent name servers (which I do have, since adding backup name servers seems like it should be a good thing).
Meanwhile, on another machine on the same network, I run a more recent non-LTS xubuntu (dnsmasq-base 2.71-1), and it doesn't have this problem. Checking the syslog there, the events are mostly the same as I've quoted above, but the dns server order at the end is the same as supplied by dhcp. I can see 3 reasons why the newer dnsmasq might work: - some clever strategy from bug #1003842 was adopted - the non-reversed order of the dns servers fixed it - pure luck I'm hoping it is one of the first 2 or the combination of both :-) Meanwhile I've tried your workaround and it seems to work. I might add though that I didn't choose to use dnsmasq but that was done by default when installing. (That too, is discussed in #1003842). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449083 Title: dnsmasq reverses order of dns servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1449083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
