Bug 11270 - [REQUEST]: DNS Blocking Lists
Summary: [REQUEST]: DNS Blocking Lists
Status: CLOSED DEFERRED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: all All
: - Unknown - Balancing
Assignee: Assigned to nobody - feel free to grab it and work on it
QA Contact:
URL:
Keywords: NewFeature
Depends on:
Blocks:
 
Reported: 2016-12-11 17:44 UTC by Tom Rymes
Modified: 2019-11-12 13:08 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Rymes 2016-12-11 17:44:29 UTC
As discussed in this thread in the forum: https://forum.ipfire.org/viewtopic.php?f=27&t=17733&start=15

Some users are using DNS Block lists to block malicious hosts and Add servers. It would be a great feature if this functionality was provided in the WUI. Users could choose which lists they wished to enable and have the list periodically updated and implemented as blocked in unbound.
Comment 1 Tom Rymes 2018-02-06 21:37:53 UTC
Just a clarification: there is a typo in my first comment, it should be "Ad servers", not "Add servers". The point is to block advertisements.

I still think that this could be a nice feature addition.
Comment 2 Wayne 2019-03-06 15:34:36 UTC
This would be a nice to have. Ran host's list blockers for many years but this is much easier way to go, only run the block list on firewall. Works for any client machine. Add a rule to block external DNS and you know the list is always used.

Another forum link about this to add to Tom's first post. https://forum.ipfire.org/viewtopic.php?f=50&t=17787
Comment 3 Michael Tremer 2019-11-12 13:08:44 UTC
People who are interested in this seem to be low on time to build this:

> https://lists.ipfire.org/pipermail/development/2019-November/006582.html

There seem to be some people against this, because it is not a very elegant way to achieve what people want to achieve.

I will close this for now. Please continue the debate on the mailing list first before considering to re-open this ticket.