Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
Currently the flexibility of the DNSBL system is Unbound is somewhat limited. In the old situation Unbound startup time would grow linearly with the size of the blocklist, and since Unbound restarts often to account for system changes, this has quite the impact. This was later improved this by administrating blocklist entries dynamically, but it was still not ideal. Due to the internals of Unbound, the memory impact is also very large.
Describe the solution you like
A new system that uses the python extension in Unbound to programmatically handle blocklists, which can also be extended for other uses in the future.
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
Currently the flexibility of the DNSBL system is Unbound is somewhat limited. In the old situation Unbound startup time would grow linearly with the size of the blocklist, and since Unbound restarts often to account for system changes, this has quite the impact. This was later improved this by administrating blocklist entries dynamically, but it was still not ideal. Due to the internals of Unbound, the memory impact is also very large.
Describe the solution you like
A new system that uses the python extension in Unbound to programmatically handle blocklists, which can also be extended for other uses in the future.