A short term hack seems to be to change the location of the resolv.conf pointed to in the daemon script, /etc/init.d/dnsmasq.
I changed it to point to /etc/resolvconf/resolv.conf.d/original instead of /var/run/dnsmasq/resolv.conf and that seems to have worked around the problem. >From what I can tell, until the interface with DHCP is brought down then up, the resolvconf update script for dnsmasq is not getting the DNS servers given by DHCP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875950 Title: /var/run/dnsmasq/resolv.conf empty on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/875950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs