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

    Pfsense in HA and pfblockerNG DNS query

    Scheduled Pinned Locked Moved pfBlockerNG
    6 Posts 4 Posters 791 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.
    • R
      Rodeo21
      last edited by

      Hi all.
      I have configured two pfsense in Sync (HA) and added the pfBlockerNG module.

      Everything is working fine but I am detecting strange behavior. The dns queries arrive both on the master and on the backup, although the destination ip of the queries is that of the master. (I notice this behavior by checking the pfclockerNG alerts)

      The infrastructure expects clients to query a Microsoft DNS (AD) first.

      The Microsoft DNS server (AD) has set the pfsense master's ip as forwarder.

      However, some DNS queries also arrive on the backup pfsense.

      Some idea?

      BBcan177B 1 Reply Last reply Reply Quote 0
      • S
        SmokinMoJoe
        last edited by

        Too bad you did not get a reply, I think others might see this issue as well. I understand the Windows 10 ip stack will shotgun DNS queries to all servers in some conditions and whoever responds to the clinet first wins. In a small LAN this might be OK but I am betting that a large university like Georgia Tech might have some DNS administrators very upset.

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

          @rodeo21 Are you using pfBlockerNG-devel?

          "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/

          S 1 Reply Last reply Reply Quote 0
          • S
            SmokinMoJoe @BBcan177
            last edited by

            @bbcan177

            I just did the update today to pfBlockerNG-devel 3.0.0_8

            1 Reply Last reply Reply Quote 0
            • T
              talaverde
              last edited by

              Hi @rodeo21 I would think this would be more of an issue related to multicast and the CARP VIPs. This is the source of most HA IP issues. If DNS requests are hitting your backup node, this would mean the issue is occurring well before pfBlocker (or unbound) gets involved. Have you tried removing pfBlocker to see if the DNS issues go away (or still exist)? You'll probably have to look at different logs, but there still should be something to check.

              S 1 Reply Last reply Reply Quote 0
              • S
                SmokinMoJoe @talaverde
                last edited by

                @talaverde
                HA is a complex animal, some interfaces use CARP VIPs and packages use the XMLRPC to sync. XMLRPC has issues where you can use a dedicated user and some vendors(Snort/Cisco) did not think you could do that so they force you to use root/admin to sync your data.

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