Comment 39 for bug 998712

First the bad news.

Name resolution drops after a few minutes of inactivity (approx. 30mins).

Same phenomenon as before.

Second: The name server answers as soon as the request arrives. dnsmasq obviously takes some time to determine if it can serve the name itself.

So back to square one: disabling dnsmasq: immediate and correct name resolution (I am talking about not recognisable delays).
enabling dnsmasq the problems begin (with a difference if set to strict-order). Name resolution takes

Name resolution after reboot and resume now work fine. Unfortunately after some time it does not any more. Same symptoms as without strict-order.

Just read the man-pages:

-o serves in the order resolv.conf offers!

but here is what my resolv.conf looks like

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.1.1
search rsb.intern rsb.at

So it refers to itself.

There is no dnsmasq.conf file where the dns servers are defined (not installed by default).
Network manager just starts dnsmasq but hat no information about the network either.