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

    Custom whitelist sites still being blocked as per log?

    Scheduled Pinned Locked Moved pfBlockerNG
    4 Posts 2 Posters 605 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.
    • J
      JimPhreak
      last edited by

      I'm trying to get a certain site to load properly while having DNSBL enabled.  I've added the site to my custom whitelist but the dnsbl.log is showing the following still for the site:

      DNSBL Reject HTTPS,Apr 24 17:17:52,supportxmr.com

      I've added supportxmr.com with and without the "." before it into my custom white list, running and update, and then doing a flushdns on the local client.  Above is still what shows up in the log.

      What am I missing?

      1 Reply Last reply Reply Quote 0
      • RonpfSR
        RonpfS
        last edited by

        On my system, with TLD enabled, it's flagged as a TLD, so you should put a dot in front of the domain name: .supportxmr.com

        Did you do a Force Reload DNSBL?
        You can see the whitelisted domain names in the pfblockNG.log file

        [ EasyListPrivacy ] Downloading update [ 04/22/18 23:17:30 ] .. 200 OK.
          Whitelist: adobedtm.com|googletagmanager.com|omtrdc.net|optimizely.com|
          –--------------------------------------------------------------------
          Orig.    Unique    # Dups    # White    # TOP1M    Final               
          ----------------------------------------------------------------------
          3459    3435      351        4          0          3080               
          ----------------------------------------------------------------------
          IPv4 count=16

        2.4.5-RELEASE-p1 (amd64)
        Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
        Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

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

          @RonpfS:

          On my system, with TLD enabled, it's flagged as a TLD, so you should put a dot in front of the domain name: .supportxmr.com

          Did you do a Force Reload DNSBL?
          You can see the whitelisted domain names in the pfblockNG.log file

          [ EasyListPrivacy ] Downloading update [ 04/22/18 23:17:30 ] .. 200 OK.
            Whitelist: adobedtm.com|googletagmanager.com|omtrdc.net|optimizely.com|
            –--------------------------------------------------------------------
            Orig.    Unique    # Dups    # White    # TOP1M    Final               
            ----------------------------------------------------------------------
            3459    3435      351        4          0          3080               
            ----------------------------------------------------------------------
            IPv4 count=16

          Ahhh, I was doing a force update but not a force reload of DNSBL.  That fixed it.  Thank you!

          1 Reply Last reply Reply Quote 0
          • RonpfSR
            RonpfS
            last edited by

            When I click on the infoblock I see :

            Note: These entries are only Whitelisted when Feeds are downloaded or on a 'Force Reload'.

            ::)

            2.4.5-RELEASE-p1 (amd64)
            Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
            Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

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