>
>
> How is the 'ban-hosts' file updated? Does it need a SIGHUP to dnsmasq
> (please not another thing hanging off SIGHUP) Does it need a complete
> restart?
>
> If 'ban-hosts' can be dynamically updated then I can see some value in it,
> until then it looks like it's a syntax nicety. Perhaps t
On 08/08/17 09:23, wkitt...@gmail.com wrote:
On 08/08/2017 04:06 AM, Matteo Croce wrote:
2017-08-08 4:26 GMT+02:00 :
On 08/07/2017 06:02 PM, Matteo Croce wrote:
I propose adding an option to allow banning some domains.
add `--ban-hosts' which accepts a file name which contains a list of
d
On 08/08/2017 04:06 AM, Matteo Croce wrote:
2017-08-08 4:26 GMT+02:00 :
On 08/07/2017 06:02 PM, Matteo Croce wrote:
I propose adding an option to allow banning some domains.
add `--ban-hosts' which accepts a file name which contains a list of
domains to block, one per line.
Domains are block
2017-08-08 4:26 GMT+02:00 :
> On 08/07/2017 06:02 PM, Matteo Croce wrote:
>>
>> I propose adding an option to allow banning some domains.
>>
>> add `--ban-hosts' which accepts a file name which contains a list of
>> domains to block, one per line.
>> Domains are blocked by simply returning NXDOMAI
On 08/07/2017 06:02 PM, Matteo Croce wrote:
I propose adding an option to allow banning some domains.
add `--ban-hosts' which accepts a file name which contains a list of
domains to block, one per line.
Domains are blocked by simply returning NXDOMAIN.
is the following in dnsmasq.conf broken?
I propose adding an option to allow banning some domains.
add `--ban-hosts' which accepts a file name which contains a list of
domains to block, one per line.
Domains are blocked by simply returning NXDOMAIN.
TODO: allow blocking also subdomains via wildcard: eg. *.example.com
---
dnsmasq.conf.e
