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

    pfBlockerNG-devel with AdGuard DNSBL not working -- HELP

    Scheduled Pinned Locked Moved pfBlockerNG
    2 Posts 2 Posters 1.5k 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.
    • S
      ssingh
      last edited by ssingh

      Hi,

      I am new to pfSense community and I have pfSense 4100 box with pfBlockerNG-devel and I also installed the Adguard home in my pfSense box. I followed this article : https://broadbandforum.co/threads/installing-adguard-home-on-pfsense.205884/

      After the setup, I am able to get adguard up and running in pfsense box but the problem i am having is the DNSBL is broken on pfsense now, as you can see the screenshot below it does not filter anything on DNSBL but everything goes to the Adguard, It is still blocking the IP somehow.

      My goal is to create a setup where first pfsense DNSBL gets processed for the block and then it should go to the adguard for DNS resolve and process the blocklist on adguard that way I am able to take advantage of both the DNS blocklists and make sure nothing is being missed. can someone please help me figure this out? I have tried re-installing the pfblockerng and restarting the Pfsense but nothing has helped yet to fix why pfblockerng is not processing the DNS block/Packets :(

      I would really appreciate any help I could get with this.

      7c4e873c-25be-4412-b9a7-be84e4cf05c8-image.png
      0f2d1b1f-8bc8-4ccb-9c37-b033a76bea0a-image.png

      keyserK 1 Reply Last reply Reply Quote 0
      • keyserK
        keyser Rebel Alliance @ssingh
        last edited by

        @ssingh That’s going to take some “creative” configuration to work. PfSense comes with the UNBOUND DNS server which pfBlockerNG-devel modifies to answer DNS requests pr. Your allowed/denied lists. Adguard is another DNS filter service on its own, so now you have two competing services wanting to offer DNS services on port 53 - only one can prevail (seems adguard did in your case).
        I would seriously recommend you keep adguard away from pfsense itself. It’s not designed to run on there, and pfSense’s default setup and UI settings expects its own services to resolve DNS.

        Unless you know what you are doing, you’ll never get it to work as it would require quite at lot of “tinkering and custom setup”.

        pfBlockerNG-devel can do everyting adguard does - you can even have it use the same blocklists, so there is no need for both.
        So stick with that and stay away from the adguard service.

        It you insist, then install adguard on a raspberry pi and have pfsense and unbound use that as an upstream DNS server (forwarding mode).

        Love the no fuss of using the official appliances :-)

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