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

    DNS Resolving

    Scheduled Pinned Locked Moved DHCP and DNS
    8 Posts 4 Posters 1.7k 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.
    • J Offline
      Jamerson
      last edited by

      Hi Guys
      i am using Pfsense behind a domain controller .
      my Domain controller is forwarding DNS request to the Pfsense.
      Pfsense is using my ISP DNS.
      when i add the pfsense into the DNS forwarder on my Domain controller somehow it doesn't resolve it !

      Pfsense is the gateway of my Domain controller.
      i can pig Pfsense from the Domain controller and other computers on the network.
      i can browse to the internet
      i can ping the internet using name and ip

      Pfsense Version is 2.2.2

      please advise

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

        "when i add the pfsense into the DNS forwarder on my Domain controller somehow it doesn't resolve it !"

        Doesn't resolve what??  What are you clients using for dns?

        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
        • J Offline
          Jamerson
          last edited by

          @johnpoz:

          "when i add the pfsense into the DNS forwarder on my Domain controller somehow it doesn't resolve it !"

          Doesn't resolve what??  What are you clients using for dns?

          My Client using My Domain controller as DNS, my Pfsense using my External DNS as forwarder "ISP DNS

          when i add the Pfsense on the DNS Manager >> Forwarders >>> Pfsense IP it said "Unable to resolve "

          i did it the otherway arround.

          Pfsense forward the DNS Query to my Domain controller, and my domain controller to the ISP DNS. and it works.
          dont know why pfsense wouldnt resolve with my Domain controller !

          1 Reply Last reply Reply Quote 0
          • T Offline
            technical ownage
            last edited by

            If all the computers on your network are already using the domain controller for DNS, then the forwarders on the domain controller should just go directly to the ISP's dns servers.

            Like such:

            Clients > Domain Controller DNS >ISP DNS

            Just use pfsense as the gateway.

            Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

            1 Reply Last reply Reply Quote 0
            • G Offline
              gjaltemba
              last edited by

              @Jamerson:

              when i add the Pfsense on the DNS Manager >> Forwarders >>> Pfsense IP it said "Unable to resolve "

              DNS Manager is unable to find (resolve) FQDN of your pfsense IP. This does not impact the use of pfsense as a forwarder in DNS Manager. If it bothers you then try adding a PTR record for your pfsense IP in the Reverse Lookup Zone in DNS Manager.

              1 Reply Last reply Reply Quote 0
              • J Offline
                Jamerson
                last edited by

                @technical:

                If all the computers on your network are already using the domain controller for DNS, then the forwarders on the domain controller should just go directly to the ISP's dns servers.

                Like such:

                Clients > Domain Controller DNS >ISP DNS

                Just use pfsense as the gateway.

                Pfsense need to use the ISP DNS in this matter ?
                am i right ?

                thank you

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

                  what?  pfsense can use either something you forward to be it your isp dns or opendns or level3 4.2.2.2 or could be its own resolver.  But yeah if your clients are all using ad dns, there is little point in having pfsense be another hop in your dns queries.  Either have your ad dns forward to something or have it directly resolve as well.

                  You could even point pfsense to your AD dns if you wanted too.

                  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
                  • J Offline
                    Jamerson
                    last edited by

                    @johnpoz:

                    what?  pfsense can use either something you forward to be it your isp dns or opendns or level3 4.2.2.2 or could be its own resolver.  But yeah if your clients are all using ad dns, there is little point in having pfsense be another hop in your dns queries.  Either have your ad dns forward to something or have it directly resolve as well.

                    You could even point pfsense to your AD dns if you wanted too.

                    Thank you
                    this what i configured now.
                    why the ISP dns wasnt resolving today the ISP Modem was dead ! just figured out

                    New Modem is sent.

                    Thank you guys for the help

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