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

    Dnsbl service not starting

    Scheduled Pinned Locked Moved pfBlockerNG
    6 Posts 3 Posters 2.0k 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.
    • M
      moosport
      last edited by

      Install pfblocker and enabled dnsbl but the service is not running. Check the logs in /var/log and did not see anything that stands out.

      http://imgur.com/a/nilVk

      1 Reply Last reply Reply Quote 0
      • BBcan177B
        BBcan177 Moderator
        last edited by

        Did you enable the DNS Resolver?
        Did you configure the Interface and port settings in the DNSBL General Tab?
        Once you have configured those and added some feeds to the DNSBL Feeds tab, you can goto the "Update" tab and then run a Force Update to enable the settings.

        "Experience is something you don't get until just after you need it."

        Website: http://pfBlockerNG.com
        Twitter: @BBcan177  #pfBlockerNG
        Reddit: https://www.reddit.com/r/pfBlockerNG/new/

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

          Are you refering the DNS Resolver under Services? No its not enabled.

          The listening port and interface is configured. There are feeds added.

          1 Reply Last reply Reply Quote 0
          • BBcan177B
            BBcan177 Moderator
            last edited by

            DNSBL requires the DNS Resolver to be enabled.

            "Experience is something you don't get until just after you need it."

            Website: http://pfBlockerNG.com
            Twitter: @BBcan177  #pfBlockerNG
            Reddit: https://www.reddit.com/r/pfBlockerNG/new/

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

              @BBcan177:

              DNSBL requires the DNS Resolver to be enabled.

              Enabled it and change the port for Forwarder. The service still failed.

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

                Sorry for bringing up such an old post, but the recommendations @BBcan177 mentioned worked for me. In my case, I had to make sure the two ports used for HTTP and HTTPS traffic didn't overlap with any other rules I had already defined.

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