Nice finding. But the lists aren’t in RPZ format.
The files in unbound directory contain lines that could be included in unbound.conf, but the auto update mechanism by a SOA record doesn’t exist.
It could be compiled to the RPZ format. But this would be demand an extra fcrontab entry, f.e., for updating ( and a reload operation of unbound, which would reset the update timers ).
Did not check the quality of the several converters ( source syntax → RPZ syntax ).
But all programs don’t write a SOA record for auto update. This is mandatory for the process implemented by @jon !
But auto updating by unbound doesn’t function with these list anyway.
The idea of the RPZ addon is
define a RPZ in unbound configuration with a source for a filter list
this list begins with a SOA record with an entry for the update period
unbound uses this record to update the list internally
List not adhering to this model must be loaded externally and announced to unbound by a reload operation, with the issues described in the RPZ wiki article.
I was successful in converting and importing the list into rpz with jons awesome beta-addon, but I’m not sure its worth it since you have to use http from the green ip of the firewall for unbound to do the import due to self signed certs. if anyone wants to know how i did it, i can explain via pm… ive hijacked jons thread a bit much and apologize @jon