Comment 10 for bug 1031350

I also had this issue after an upgrade from Precise, but /etc/NetworkManager/dnsmasq.d was there.

I found I had a permanantly blank resolv.conf, and had to

 dpkg-reconfigure resolvconf

and say 'Yes' to "Prepare /etc/resolv.conf for dynamic updates?"
and I said 'No' when it asked me if it should append my current contents to the config file.

It now works, with /etc/resolv.conf pointing at 127.0.1.1 which I presume means that it's delegating to dnsmasq on localhost.