[Bug 998712] Re: domain name completion broken when dnsmasq is used

[Thomas Hood]

My guess is that this bug is fundamentally bug #1003842 with the twist
that sometimes the lookup succeeds if the fully qualified internal
domain name is given on the command line explicitly.

(I don't think it's a coincidence that both Wolf and Reggie are on
networks with non-equivalent nameservers.)

That is, using Wolf's example, "ping s4" fails because 's4' can't be
resolved (as expected) and then 's4.rsb.intern' also can't be resolved
because of bug #1003842.

The remaining question is why "ping s4.rsb.intern" *does* work. And why
did "dig s4 +search" succeed in Wolf's last experiment? It's possible
that in these cases dnsmasq happened to talk to the internal nameserver
instead of the external one.

If this hypothesis is correct then running nm-dnsmasq in strict-order
mode should also fix the problem. If you are running Ubuntu 12.10 then
please try running nm-dnsmasq in strict-order mode. To put nm-dnsmasq
into strict-order mode, create a file
/etc/NetworkManager/dnsmasq.d/strictorder with the single line "strict-
order" and then "sudo restart network-manager". NM-dnsmasq should now be
running in strict-order mode and everything should be working perfectly.
:)  This method doesn't work in Ubuntu 12.04 which lacks
/etc/NetworkManager/dnsmasq.d/.

-- 
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/998712

Title:
  domain name completion broken when dnsmasq is used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/998712/+subscriptions