Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    DNS Blacklist, New Package! Check it out.

    Scheduled Pinned Locked Moved pfSense Packages
    153 Posts 56 Posters 129.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      cybrsrfr
      last edited by

      Here is the original blacklist that was going to be used.
      http://urlblacklist.com/

      I didn't use it in the final version of the package because I didn't feel that redistribution of that list was the ethical thing to do when the website that provides the list is trying to sell it. They provide the entire list for download and payment is on an honor basis as stated on their website. Their intent is really to sell it for a subscription. I did not notice this when I started building this package. When I noticed they were trying to sell the list they had compiled I could not with good conscious redistribute urlblacklist.com's list. If someone wants to use that list and pay for the subscription they can do so by editing the domain lists and adding the categories as I described in an earlier post.
      http://urlblacklist.com/?sec=subscribe

      Here is a few more choices of DNS blacklists.
      http://www.squidguard.org/blacklists.html

      Anyone can edit the list that the package comes with. In order for an alternative customized list to be used in the DNS blacklist package it must be compiled ethically and legally or I will not commit it to the package. For example it wouldn't be ethical to use lists from urlblacklist.com or other lists that don't offer the list in freely. Unless you obtain permission directly from them to use the list for such a purpose.

      The list from http://cri.univ-tlse1.fr/blacklists/index_en.php says on their website 'can be used with many commercial or free software' therefore it is ethical to use their list for the DNS Blacklist package.

      1 Reply Last reply Reply Quote 0
      • X
        xa0z
        last edited by

        Hmm, so I guess there isn't a need for me to continue on with the project.  It is just pointless for me to try and do one thing and then have it all changed to not be the way it was when I started it.

        I already said I was going to build my own database list but what's the point, I don't need to supply something that anyone can just grab from all over the net to use.

        I'm glad for the help I got when I started writing the project but if I am being phased out, which it so seems I am, then I guess my input, or work is useless.

        1 Reply Last reply Reply Quote 0
        • S
          Supermule Banned
          last edited by

          If this isn't supported and maintained, pls. inform me how to delete it completely! It wont go away…..any way I do it.

          1 Reply Last reply Reply Quote 0
          • X
            xa0z
            last edited by

            Okay, what you need to do is "Remove" the package like normal… then Re-Install it like normal.  Then the new version has the fixes to take care of the problems you're having.  You can then remove it to completely remove it, or you can keep using it.

            My only problem is that this is starting to move a direction in which I don't seem to have anymore say so in the project.  I'm not saying anything bad, and I'm not about to put mcrane down, he's a great guy and has helped me a great deal with stuff, but I just wish the project I started, and wrote part of... I had some control over.

            1 Reply Last reply Reply Quote 0
            • S
              Supermule Banned
              last edited by

              That is quite understandable…..:)

              You have my support for the project, but it seems that the way the list is generated and the source of the data, is the big hurdle???

              1 Reply Last reply Reply Quote 0
              • X
                xa0z
                last edited by

                I want to compile my own database.  I want to get it as simple as possible where specific rated categories are available for certin things.  I want to remove all the IPs in the database and use only hostnames (for now) to help keep it clean.  Web Browsers don't do reverse lookups so having all those extra useless items is a waste of RAM.

                I will try my best to keep with the program, just want to make sure it stays on track.  I mean the whole point to me starting this was to help out, and if it's not helping me, how can it help others?

                1 Reply Last reply Reply Quote 0
                • S
                  Supermule Banned
                  last edited by

                  Exactly. :)

                  Keep it up! You are on the right track….IP's change. Domainnames do not as often....So it is a good argument.

                  1 Reply Last reply Reply Quote 0
                  • C
                    cybrsrfr
                    last edited by

                    The problem is the list. As I stated before it has to be created ethically. That is compiled from free lists where the owners give their permission.

                    I will not commit something to pfSense that makes me an accessory to stealing. That is why I refused to commit the package with the previous list. If I did this I would expect to get my commit authority revoked.

                    It is not impossible to find lists that are free for any use and supplement them, and improve them with your own domains you and others find while searching.

                    1 Reply Last reply Reply Quote 0
                    • X
                      xa0z
                      last edited by

                      That is exactly what I'm doing.  I'm not worried about the urlBlacklists database anymore.  I am just saying that I'm getting the database taken care of on my own, and it will be greatly categorizied.

                      1 Reply Last reply Reply Quote 0
                      • D
                        Davc
                        last edited by

                        I think this is a good project, if the DNS Blacklist is good and effectively use. Surely there will be people supported and willing to donate some subscription fee to maintain the Blacklist and the project itself in this Pfsense forum/members.

                        I am no expert in here, but there are people who might (already) using OpenDNS to filter, as long as this project don't run the same track as the OpenDNS or able to offer more than OpenDNS. I think there are light on this projects.

                        Good Work !!  ;)

                        1 Reply Last reply Reply Quote 0
                        • J
                          jan.gestre
                          last edited by

                          Hi Davc,

                          I've tried DNS blacklist in one of my pfSense box but it broke the dns forwarder service, after installation the dnsmasq service stopped and can't be restarted even after repeated tries and reboot. I uninstalled the aforementioned package but I still can't start the dnsmasq service,I had to examine other working boxes to see what files have been added or changed by the DNS blacklist package, it added the dnsmasq.conf which I've deleted and my dnsmasq service finally started.

                          Did I missed something?

                          Regards,

                          Jan

                          1 Reply Last reply Reply Quote 0
                          • C
                            cybrsrfr
                            last edited by

                            When you tried to start dnsmasq. If you would have looked at the Diagnostics: System logs: System and looked for errors inr regards to dnsmasq then you should be ablt to find a description why it refused to start.

                            1 Reply Last reply Reply Quote 0
                            • J
                              jigpe
                              last edited by

                              Good job :)

                              I have Q.. How to block HTTPS? (except legit HTTPS)?

                              jigp

                              1 Reply Last reply Reply Quote 0
                              • D
                                Davc
                                last edited by

                                Mine is running fine.

                                1.2.3-RC2
                                built on Sat Jul 18 19:19:52 EDT 2009
                                FreeBSD 7.2-RELEASE-p2 i386

                                DNS Blacklist 0.2.4

                                Yes, after the installation of DNS Blacklist. I have to manual restart the services.

                                My Box run in Bridge mode, I guess yours are different in NAT mode.

                                Davc

                                1 Reply Last reply Reply Quote 0
                                • X
                                  xa0z
                                  last edited by

                                  After installing DNS Blacklist you shouldn't be required to restart dnsmasq as nothing is edited that pertains to dnsmasq at the time.  DNS Blacklist adds the dnsmasq.conf, and dnsmasq.blacklist.conf files into /usr/local/etc/.  When DNS Blacklist is enabled it adds a string into dnsmasq.conf to load the dnsmasq.blacklist.conf file, then restarts dnsmasq.  Any of the categories you select are entered within the dnsmasq.blacklist.conf file and that is what allows us to filter dns querys to the local server.

                                  I am in no way out to seek any money from anyone for the blacklist database I'm putting together.  I can maintain a "main blacklist" but users would be free to add their own domains that aren't already listed.  Here soon I'll work on adding a custom Blacklist/Whitelist text area for you to enter your own on the fly.

                                  If you want to block all https, you need to put a block on dport:443, that isn't associated with DNS Blacklist.

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    jigpe
                                    last edited by

                                    | If you want to block all https, you need to put a block on dport:443, that isn't associated with DNS Blacklist.

                                    • I dont want to block 443 from Firewall LAn.. Some users needs to access legitimate https sites…. Kindly show us the right way xa0z? Thanks

                                    jigp |

                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      boblmartens
                                      last edited by

                                      I can't really thank you enough for putting in the effort for this package. This is exactly what my place of employment has been looking for to push us off of using WatchGuard Fireboxes and moving to a custom-built firewall running pfSense.

                                      Thanks, and if you need any help, let me know!

                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        mastablastaz
                                        last edited by

                                        Is that package the same as using squid with 0 cache + squidGuard using the urlblacklist.com filter?

                                        1 Reply Last reply Reply Quote 0
                                        • X
                                          xa0z
                                          last edited by

                                          Not really, but the same concept mainly.  We're not using proxies, and are just making hostnames that you don't want allowed on your network to resolve to a specific IP rather than loading a proxy, etc.

                                          So for instance, if you have  facebook.com  added to the category of denied hosts, then if anyone tried to resolve the forementioned host name then it would resolve to the IP I currently have set in the config, which is a Google IP.  So all requests would be for example like so…    http://www.facebook.com/games/mafiawars, would actually load http://www.google.com/games/mafiawars, which would fail, and alert you so.

                                          I do have improvement ideas I'd like to implement in, but I won't be able to submit/commit them until mcrane is ready to do so and currently he has other projects he's working on.

                                          1 Reply Last reply Reply Quote 0
                                          • T
                                            Tracktor
                                            last edited by

                                            As I understand the LAN DNS must be the pfsense DNS forwarder in order to make this package work?

                                            10X for your effort

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.