Comment 13 for bug 998712

On the affected system when it is manifesting the problem you reported (can't resolve names), is named running locally? (In your original submission you said that bind was running.) What role does this named play in your network? How is it configured? What happens if you stop this named? And then restart network-manager?

All these questions pertain, obviously, to the hypothesis that local named may be interfering with local dnsmasq.