On Fri, Jan 9, 2015 at 12:25 PM, Steven Barth wrote:
> Our dnsmasq init script registers /tmp/dnsmasq.d as an additional
> configuration dir, so you can place files there and restart it. However I'm
> not sure as to how much we want netifd to do dnsmasq-specific stuff or how
> we would do it.
Wel
Our dnsmasq init script registers /tmp/dnsmasq.d as an additional
configuration dir, so you can place files there and restart it. However
I'm not sure as to how much we want netifd to do dnsmasq-specific stuff
or how we would do it.
Of course the bad thing here again is that dnsmasq doesn't su
On Fri, Jan 9, 2015 at 9:48 AM, Hans Dedecker wrote:
> On Thu, Jan 8, 2015 at 5:43 PM, Nikos Mavrogiannopoulos
> wrote:
>> Currently a protocol can register a dns server with netifd using the
>> proto_add_dns_server function. That however, does not allow
>> registering a DNS server for a specific
On Thu, Jan 8, 2015 at 5:43 PM, Nikos Mavrogiannopoulos
wrote:
> Currently a protocol can register a dns server with netifd using the
> proto_add_dns_server function. That however, does not allow
> registering a DNS server for a specific domain. I checked the netifd
> code and there is no provisio
Currently a protocol can register a dns server with netifd using the
proto_add_dns_server function. That however, does not allow
registering a DNS server for a specific domain. I checked the netifd
code and there is no provision for that. Would it make sense to add
such functionality to netifd, or
