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

    Query refused

    DHCP and DNS
    2
    3
    969
    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
      mk0001
      last edited by

      Hi, when trying nslookup, I am getting the ' Query refused' error on a Win10 device.

      My setup is a bit complicated.

      I have a L3 switch doing routing and static routes from pfSense to it. DNS Resolver is enabled for ALL interfaces but my educated guess is that it "does not like" when a dns request comes from an IP that does not match its interfaces. nslookup works OK for clients with IPs matching the IP of pfsense. It fails when I have a client behind a L3 switch with a different IP than the LAN interface of pfSense. DNS is pointing to the LAN of pfSense (I use pfBlocker). Routing works OK. I can ping the Internet through pfSense from a client behind my L3 switch, however, nslookup shows 'query refused'.

      Any ideas?

      bingo600B 1 Reply Last reply Reply Quote 0
      • bingo600B
        bingo600 @mk0001
        last edited by

        @mk0001

        You are prob. 100% correct

        Unbound (resolver) doesn't like "Non interface" Networks
        Unless you add the "unknown" nets in the ACL section.

        a05ae7e8-cdc3-4c7b-b137-5a76b20fc0ce-image.png

        Just add the "unknown's there"

        Services --> DNS Resolver --> Access Lists

        /Bingo

        If you find my answer useful - Please give the post a šŸ‘ - "thumbs up"

        pfSense+ 23.05.1 (ZFS)

        QOTOM-Q355G4 Quad Lan.
        CPUĀ  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
        LANĀ  : 4 x Intel 211, DiskĀ  : 240G SAMSUNG MZ7L3240HCHQ SSD

        M 1 Reply Last reply Reply Quote 1
        • M
          mk0001 @bingo600
          last edited by

          @bingo600
          A quick fix. It is working now.

          Thank you!

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