Thanks for this bug report. Since resolvconf appears to be populating /etc/resolv.conf as designed, but dnsmasq is failing to resolve for you, I'm reassigning this to network-manager (the package responsible for setting up dnsmasq this way on the desktop).
Since you're getting an answer at all, dnsmasq is clearly running.
And you don't have any other nameserver implementations installed locally (e.g., bind9) that could be taking the socket instead of dnsmasq, correct?
Does reducing the number of nameservers registered have any effect on whether dnsmasq works correctly?
Thanks for this bug report. Since resolvconf appears to be populating /etc/resolv.conf as designed, but dnsmasq is failing to resolve for you, I'm reassigning this to network-manager (the package responsible for setting up dnsmasq this way on the desktop).
Since you're getting an answer at all, dnsmasq is clearly running.
And you don't have any other nameserver implementations installed locally (e.g., bind9) that could be taking the socket instead of dnsmasq, correct?
Does reducing the number of nameservers registered have any effect on whether dnsmasq works correctly?