Closed steventblack closed 7 years ago
The issue at heart seems to be that all the different zones for the blocked domains in the configuration file ad-blocker.db
referencing the same zone file named/etc/zone/master/null.zone.file
is a prohibited configuration. Need to find a workaround which (hopefully) doesn't entail generating a copy of the zone file for each blocked domain.
Disallowing updates for the zone seems to have resolved the issue.
Need to change the line in named/etc/zone/data/null.data.file
to disallow updates:
zone "null.zone.file" {
type master;
file "/etc/zone/master/null.zone.file";
allow-transfer {none;};
allow-update {none;};
allow-query {any;};
};
Leaving issue open until this is ensured either through Synology's interface tool or via programmatic means.
Updated readme to include appropriate setting of "Limit zone updates".
Restarting the DNS server seems to result in a torrent of error messages:
writable file '/etc/zone/master/null.zone.file': already in use: /etc/zone/data/null.zone.file:3
the
/etc/zone/data/null.zone.file:3
phrase seems to refer to this line of that file:file "/etc/zone/master/null.zone.file";
A very fast google on the issue seems to revolve around the deprecated support for a dynamically updating a master DNS file. The wildcard identifier (match everything) coupled with the explicit include of the ad-blocker.db file is probably causing some sort of friction. Need to sort it out so that it operates a bit smoother.