Navigation

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

    Single Host being blocked by pFBlockerNG

    pfBlockerNG
    2
    2
    43
    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.
    • A
      aiwa last edited by

      I am running pfBlockerNG ver. 2.1.4_22 on pFsense ver. 2.4.5-RELEASE-p1

      I have a single Windows 10 host on the network that cannot resolve FQDN entries using nslookup, server IP address 192.168.25.254. I have a firewall rule in place, to force ALL hosts on the network to use the pFsense router only for their DNS lookups. I can perform nslookup’s on all other hosts except for one at IP address 192.168.25.14.

      I created a custom rule, under firewall rules, to allow the blocked host to use a custom DNS at IP address 208.67.222.222 instead of the local pfSense DNS at IP address 192.168.25.254, now the client can resolve FQDN entries using nslookup. Where can I look too see why this one host cannot resolve FQDN using the local pFsense DNS? Any help would be greatly appreciated!

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

        I'm curious on how you determined that pfBlockerNG is the root cause of the issue?

        If I were troubleshooting, I would create a firewall rule:
        Source = 192.168.25.14:*
        Destination = *:53
        Enable logging and move it to the top of the rules for that interface and see what it captures.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post