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

    DNSBL bypass for subnet stopped working

    Scheduled Pinned Locked Moved pfBlockerNG
    3 Posts 2 Posters 445 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.
    • B
      bhjitsense
      last edited by bhjitsense

      A while back, I followed some advice on here on how to bypass DNSBL for a particular subnet. It worked fine, but I noticed for at least the last couple of days, the bypassed subnet is going through DNSBL again. This is my current configuration;

      server:
          access-control-view: 192.168.10.0/24 dnsbl
          access-control-view: 192.168.20.0/24 bypass
          access-control-view: 192.168.30.0/24 dnsbl
          access-control-view: 192.168.40.0/24 dnsbl
          access-control-view: 192.168.50.0/24 dnsbl
      view:
          name: "bypass"
          view-first: yes
      view:
          name: "dnsbl"
          view-first: yes
      
      server:include: /var/unbound/pfb_dnsbl.*conf
      

      The 192.168.20.0/24 subnet is a Guest Network, for which I wanted DNSBL to be bypassed, but I see now I have reports of devices hitting DNSBL from this subnet. I have recently upgraded pfsense to the latest version, but I'm not exactly sure when this stopped working. Does anyone have any advice?

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

        @bhjitsense said in DNSBL bypass stopped working:

        server:
        access-control-view: 192.168.10.0/24 dnsbl
        access-control-view: 192.168.20.0/24 bypass
        access-control-view: 192.168.30.0/24 dnsbl
        access-control-view: 192.168.40.0/24 dnsbl
        access-control-view: 192.168.50.0/24 dnsbl
        view:
        name: "bypass"
        view-first: yes
        view:
        name: "dnsbl"
        view-first: yes

        server:include: /var/unbound/pfb_dnsbl.*conf

        remove the 'server' from the last line: server:include: /var/unbound/pfb_dnsbl.*conf
        Everytime you change the dnsbl settings in pfblocker, you will need to remove that 'server' from the line inside unbound dns resolver.

        It should be:

        include: /var/unbound/pfb_dnsbl.*conf

        dead on arrival, nowhere to be found.

        B 1 Reply Last reply Reply Quote 0
        • B
          bhjitsense @mcury
          last edited by

          @mcury
          Wow! Okay. Now I think I had read that somewhere. Thanks for the help.

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