The hypothesis was that named started before dnsmasq, preventing dnsmasq from binding port 53 on 127.0.0.1. But the hypothesis is false, since you are not running named after all.
Returning to your dig output, it can be summarized as follows. dig s4 -> FAILURE dig @10.1.0.4 s4 -> FAILURE dig @10.1.0.4 s4.rsb.intern -> SUCCESS (Wolf did something here) dig s4 -> FAILURE ping s4 -> SUCCESS Notice that domain name completion failed even when the external server was specified. As Simon wrote in #4, domain name completion happens in the resolver library. So there seems to be something wrong with the resolver library: it doesn't complete domain names with the domain search suffixes when dnsmasq is in use. Am I right? Does "dig @127.0.0.1 s4.rsb.intern" work on the affected system running NM-controlled dnsmasq? ** Summary changed: - dnsmasq integration into name resolution broken + domain name completion broken when dnsmasq is used -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
