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

    DNS Fowarder just does not work.

    Scheduled Pinned Locked Moved DHCP and DNS
    5 Posts 3 Posters 886 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.
    • I Offline
      Itg
      last edited by

      Friends, there is a bug in the DNS Forwarder in pfSense 2.2.6?

      I've already set of all possible ways, following which sends various manuals, but all show the same thing in a simple and practical. Well the fact is that computers do not resolve FQDN names when using pfSense as primary DNS, I have to open port 53 on the firewall to computers to query external DNS like 8.8.8.8, 4.2.2.2, etc.

      Can anyone give me a light?

      1 Reply Last reply Reply Quote 0
      • johnpozJ Offline
        johnpoz LAYER 8 Global Moderator
        last edited by

        The forwarder works just fine.. Whatever you issues is more than likely is PEBKAC..

        So lets see your config, lets see a query..  Where are you pointing pfsense to for dns, which is where the forwarder will send traffic.

        Here I disabled the resolver, and enabled the forwarder pointing to my isp dns.. As you can see I can resolve local stuff just fine pfsense.local.lan, I can resolve stuff outside www.google.com, As you see when doing a packet capture on pfsense, it is sending the query to my isp dns I setup, and getting a response.

        forwarderworksjustfine.png
        forwarderworksjustfine.png_thumb

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 25.07.1 | Lab VMs 2.8.1, 25.07.1

        1 Reply Last reply Reply Quote 0
        • I Offline
          Itg
          last edited by

          Thanks for the help, I will do tests later. Face I see a few different things in your image, the first is that you have selected the interfaces of the networks that will redirect DNS lookups, I was not scoring any interface. The second thing I noticed is that you marked the Strict Interface Binding option.

          :)

          1 Reply Last reply Reply Quote 0
          • johnpozJ Offline
            johnpoz LAYER 8 Global Moderator
            last edited by

            Those options should have no effect.. By default it will listen on all interfaces.  When I had played with it before I didn't want it listening on all interfaces is all.  I can show you it works with the all setting and non strict if you like.

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 25.07.1 | Lab VMs 2.8.1, 25.07.1

            1 Reply Last reply Reply Quote 0
            • D Offline
              dabigoreo
              last edited by

              Running my DNS Forwarder with no issues as well. I'm set to ALL interfaces and have 2 of the register settings checked. My DNS is pointed at OpenDNS servers.

              DNS_pfsense.JPG
              DNS_pfsense.JPG_thumb

              fw: 2.3-RELEASE(amd64)
              packages: Snort, Nmap

              system: Dell Optiplex 745 desktop
              cpu: Intel Pentium D 3.4GHz
              ram: 4GB DDR2
              wan nic: Broadcom Gbe
              lan nic: Marvell Gbe

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