Thanks for the report.
When initially installed dnsmasq is configured to integrate with
resolvconf if resolvconf is also installed. This means that dnsmasq
sends its listen address (127.0.0.1) to resolvconf and uses resolvconf's
list of available nameservers to compile its own list of upstream
nameservers. It is dnsmasq's resolvconf hook script
/etc/resolvconf/update.d/dnsmasq that generates
/var/run/dnsmasq/resolv.conf. This script gets run when /sbin/resolvconf
gets run.
In your case /var/run/dnsmasq/resolv.conf is empty or absent. This
suggests that you are not using resolvconf in the normal way, or not
using it at all.
Your /etc/resolv.conf has the correct contents: it directs the resolver
to contact dnsmasq at 127.0.0.1.
In /etc/dnsmasq.conf you have configured dnsmasq to use nameservers
listed in /etc/dnsmasq-resolv.conf. I take it that you want to use this
static list instead of the dynamic resolvconf list. In that case you
should edit /etc/default/dnsmasq and set "IGNORE_RESOLVCONF=yes". Then
dnsmasq will not be directed to look in /var/run/dnsmasq/resolv.conf.
** Changed in: dnsmasq (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1090589
Title:
Empty /var/run/dnsmasq/resolv.conf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1090589/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
