#2 is easy to implement and does solve the problem of standalone dnsmasq not starting on installation in the presence of NM+dnsmasq. What I am now wondering is how useful the resulting nameserver cascade is.
resolver ---[127.0.0.1]dnsmasq ---[127.0.0.2]nm-dnsmasq ---[8.8.8.8 or whatever]nameserver
It offers caching and service on ports other than lo, which nm-dnsmasq alone does not, but would this be better implemented by making nm-dnsmasq more configurable?
Regarding #3, I've filed a wish in upstream's bugzilla: http:// sourceware. org/bugzilla/ show_bug. cgi?id= 14242
#2 is easy to implement and does solve the problem of standalone dnsmasq not starting on installation in the presence of NM+dnsmasq. What I am now wondering is how useful the resulting nameserver cascade is.
resolver ---[127. 0.0.1]dnsmasq ---[127. 0.0.2]nm- dnsmasq ---[8.8.8.8 or whatever]nameserver
It offers caching and service on ports other than lo, which nm-dnsmasq alone does not, but would this be better implemented by making nm-dnsmasq more configurable?