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

    DNSBL doesn't block search engine links

    Scheduled Pinned Locked Moved pfBlockerNG
    3 Posts 2 Posters 639 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
      scramm
      last edited by

      I have a custom list in DNSBL that contains a few websites.  If I type xxxx.com(any blocked domain on the list) into a browser, it get's correctly pointed to 10.10.10.1 and shows a 1x1 blank image.  However, if I go to a search engine, search for xxxx, then click on a link for xxxx.com, the site loads with no issues.

      I have the unbound DNS resolver set up, and a firewall rule to block all outgoing DNS traffic.

      Can anyone help me figure out what might be going wrong here?

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

        Did you enable the "TLD" option? Without TLD, only the listed domain/sub-domain is blocked…

        So without TLD:

        example.com will be blocked
            sub.example.com will not be blocked

        With TLD:

        All sub-domains are blocked.

        "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
        • S
          scramm
          last edited by

          @BBcan177:

          Did you enable the "TLD" option? Without TLD, only the listed domain/sub-domain is blocked…

          So without TLD:

          example.com will be blocked
              sub.example.com will not be blocked

          With TLD:

          All sub-domains are blocked.

          Thanks!  I figured I was missing something simple  ::)  the search result link was going through because it had a "www." on the front.  Enabling TLD fixed it.

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